How to enable text tags
Include"use_text_tags": true in your POST /signature_request/send request body. If you omit this field, it defaults to false and tags are ignored.
Syntax
A text tag is a string placed directly in the body of your PDF document, wrapped in square brackets with identifiers separated by pipe characters:Identifiers
Field types
Important notes
- PDF format is required. Form fields may be placed incorrectly if the document is not a PDF.
- Tags remain in the rendered document. To hide a tag, set its text color to match the document background color.
-
No whitespace allowed inside tags. If you need extra horizontal space for layout, use underscores (
_) after the last identifier instead:
Form field sizing
- Height is fixed to accommodate a 12pt font.
- Width equals the rendered length of the full tag string (including brackets). Add underscores after the last identifier to make a field wider.
Validation behavior
Lumin does not validate tag syntax at the time of the API request. Instead:- A tag missing any required identifier (type, requirement, assigner) is silently ignored — it is not converted into a form field and no error is returned.
- A tag with an invalid value (e.g., wrong requirement type, or a signer index that does not exist in your
signersarray) triggers thesignature_request_invalidwebhook event after submission.
You will not receive an immediate API error for malformed tags. Subscribe to
the
signature_request_invalid webhook event to catch these issues in your
integration. See the Webhooks guide for
setup instructions.Validation errors
When a text tag is malformed or references invalid data, thesignature_request_invalid webhook event is fired with an error_code and error_message. Below are the possible validation errors:
Example webhook payload
When a text tag error is detected, thesignature_request_invalid webhook event is sent:
Example: complete request with text tags
file_url might contain:
signer1 resolves to [email protected] because that signer is at index 1 in the signers array.