# How do you validate Foxit text-tags so missing signature fields don’t fail silently?

I got a full HTML-to-PDF to eSign pipeline working fast with plain HTTP calls, and I like that the signing URL is derivable so automation doesn’t depend on email clicks. But the text-tag layer failed silently for me: the API returned success even when tags weren’t recognized, leaving literal tag text in the document and 0 required fields in the signing UI. Have you found reliable ways to detect unrecognized tags or confirm how many fields were generated before a signer can complete?

##### Post Metadata
- Posted at: 3 months ago
- Author title: Founder
- Net upvotes: 1



## Related Product
[Foxit Document Workflow APIs](https://www.g2.com/products/foxit-document-workflow-apis/reviews)

## Related Category
[E-Signature APIs](https://www.g2.com/categories/e-signature-apis)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4