PDFfiller · Schema
SignatureRequest
An eSignature workflow request that sends a PDF document to one or more recipients for signing.
PDFE-SignatureDocument-ManagementForm BuilderPDF EditingElectronic SignatureDocument Workflow
Properties
| Name | Type | Description |
|---|---|---|
| id | integer | Unique identifier for the signature request |
| document_id | integer | ID of the source template document |
| method | string | Signing method: SendToEach (each recipient signs independently) or SendToGroup (sequential envelope signing) |
| envelope_name | stringnull | Name for the signing envelope (required for SendToGroup method) |
| status | string | Current status of the signature request |
| sign_in_order | boolean | Whether recipients must sign in the defined order (SendToGroup) |
| security_pin | stringnull | PIN code required by recipients to access the document |
| callback_url | stringnull | Webhook URL for signature event notifications |
| recipients | array | List of recipients for the signature request |
| created_at | string | Timestamp when the signature request was created |
| updated_at | string | Timestamp when the signature request was last updated |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://api.pdffiller.com/v2/schemas/signature-request",
"title": "SignatureRequest",
"description": "An eSignature workflow request that sends a PDF document to one or more recipients for signing.",
"type": "object",
"properties": {
"id": {
"type": "integer",
"description": "Unique identifier for the signature request"
},
"document_id": {
"type": "integer",
"description": "ID of the source template document"
},
"method": {
"type": "string",
"enum": ["SendToEach", "SendToGroup"],
"description": "Signing method: SendToEach (each recipient signs independently) or SendToGroup (sequential envelope signing)"
},
"envelope_name": {
"type": ["string", "null"],
"description": "Name for the signing envelope (required for SendToGroup method)"
},
"status": {
"type": "string",
"enum": ["awaiting", "completed", "cancelled"],
"description": "Current status of the signature request"
},
"sign_in_order": {
"type": "boolean",
"description": "Whether recipients must sign in the defined order (SendToGroup)"
},
"security_pin": {
"type": ["string", "null"],
"description": "PIN code required by recipients to access the document"
},
"callback_url": {
"type": ["string", "null"],
"format": "uri",
"description": "Webhook URL for signature event notifications"
},
"recipients": {
"type": "array",
"description": "List of recipients for the signature request",
"items": {
"$ref": "#/definitions/Recipient"
}
},
"created_at": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the signature request was created"
},
"updated_at": {
"type": "string",
"format": "date-time",
"description": "Timestamp when the signature request was last updated"
}
},
"required": ["id", "document_id", "method", "status", "recipients"],
"definitions": {
"Recipient": {
"type": "object",
"description": "A person invited to sign or fill a signature request document",
"properties": {
"id": {
"type": "integer",
"description": "Unique identifier for the recipient"
},
"email": {
"type": "string",
"format": "email",
"description": "Recipient email address"
},
"name": {
"type": ["string", "null"],
"description": "Recipient display name"
},
"status": {
"type": "string",
"enum": ["awaiting", "signed", "cancelled"],
"description": "Recipient signing status"
},
"role": {
"type": ["integer", "null"],
"description": "Role ID assigned to this recipient (SendToGroup)"
},
"order": {
"type": ["integer", "null"],
"description": "Signing order position (SendToGroup)"
},
"phone_number": {
"type": ["string", "null"],
"description": "Phone number for SMS verification"
},
"access": {
"type": ["string", "null"],
"description": "Recipient access type (fill or sign)"
},
"message": {
"type": ["string", "null"],
"description": "Custom message sent to this recipient"
}
},
"required": ["email"]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/pdffiller-signature-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.