SignatureAPI

Cancel an in-progress SignatureAPI envelope. The envelope transitions to `canceled`. Pending recipients won't be able to access the ceremonies. Already-completed envelopes cannot be canceled (the api returns 409). If the user wants to undo a completed envelope, you must explain that signed envelopes are immutable.

cancel_envelope

Create a new SignatureAPI envelope. At minimum you must provide `title`, `documents`, and `recipients`. Documents reference uploads created via `upload_file`. If required information (e.g. recipient name/email) is missing from the user, ask before calling. Use only non-sensitive data that is necessary for the requested e-signature workflow.

create_envelope

Permanently delete a SignatureAPI envelope and its associated data. This is irreversible — CONFIRM with the user before calling, and prefer cancel_envelope if the envelope is in progress. Returns no body on success.

delete_envelope

Fetch a SignatureAPI envelope by id.

get_envelope

List envelopes for the authenticated account, most-recent first, with cursor pagination. Use this to discover existing envelopes before asking the user for an id, to check whether an envelope you'd be about to create already exists, or to answer 'what envelopes do I have?' style questions. Returns a paginated response with `data` (array of envelopes) and `links.next` / `links.previous` (opaque cursor URLs — extract the `cursor` query param to paginate).

list_envelopes

Search the public SignatureAPI documentation and return ranked excerpts with source URLs. Use this BEFORE create_envelope (or any envelope-shape question) whenever you're unsure about: field names, accepted enum values, recipient/document/place schemas, supported file formats, webhook events, authentication, embedded signing, or any concept-level question (test mode, deliverables, ceremonies, attestation, etc.). It is cheaper to search than to guess and have the envelope rejected. Returns up to `max_results` results; each result has a `title`, `url`, and a short `snippet`. Cite the `url` back to the user when explaining how something works.

search_documentation

Upload a file provided by ChatGPT Apps file handling into SignatureAPI. Use this when the user has uploaded or selected a PDF, DOCX, or PNG in ChatGPT and wants to use it as a SignatureAPI document, template, logo, or symbol asset. The `file` input is a ChatGPT file parameter; do not invent URLs. Let ChatGPT populate it from the user's uploaded or selected file. Returns a SignatureAPI upload URL. Pass `url` as `document.url` in create_envelope.

upload_file