canonical: https://jentic.com/apis/annature.com.au/annature

# Annature API

Jentic publishes the only available OpenAPI specification for Annature API, keeping it validated and agent-ready. Annature is an Australian-built digital signature platform that exposes 45 REST endpoints for sending, signing, and managing electronic envelopes end-to-end. The API covers accounts, envelopes, documents, recipients, groups, organisations, templates, signing fields, and webhook endpoints, so agents can drive the full lifecycle from envelope creation through completion notifications. Authentication uses the X-Annature-Id header API key issued per organisation.

## For AI agents

Send, sign, and track digital envelopes through Annature's 45 REST endpoints. Manages recipients, templates, and webhook callbacks for AU-compliant e-signature workflows.

## Scope

Does not handle CRM contact storage, payment collection, or contract drafting - use for digital signature envelope creation, sending, and tracking only.

## Capabilities

- Create and send signature envelopes with one or more documents and ordered recipients
- Build reusable envelope templates with pre-placed signing fields and recipient roles
- Register webhook endpoints to receive completion, decline, and view events for envelopes
- Manage account users, organisations, and groups for multi-team signing setups
- Resend verification and authentication codes to recipients who have not opened an envelope
- Retrieve completed signed PDFs and per-recipient audit trails for compliance records

## Use cases

### Contract Signing Workflow

Automate sending sales contracts or NDAs by creating an envelope via POST /v1/envelopes with the document and ordered recipients, then triggering POST /v1/envelopes/{id}/send to dispatch signing emails. Annature handles email delivery, identity prompts, and tamper-evident final PDFs without the sending app having to manage SMTP, audit logs, or signed-PDF generation. Typical implementation takes 1-2 days when reusing an existing template.

Example prompt: Create an envelope via POST /v1/envelopes with one PDF and two recipients, then call POST /v1/envelopes/{id}/send and verify the response status

### Templated Onboarding Documents

Use Annature templates for repeatable documents like employment offers or supplier onboarding packs. The agent picks a template via GET /v1/templates, fills in recipient details, and sends an envelope without re-uploading PDFs each time. This keeps signing fields, ordering, and completion rules consistent across hundreds of envelopes per month and reduces template drift.

Example prompt: Call GET /v1/templates to find the 'Employment Offer' template, then POST /v1/envelopes referencing the template ID and the new hire's name and email

### Webhook-Driven Status Tracking

Register a webhook endpoint via POST /v1/webhook-endpoints to receive envelope status changes (sent, viewed, signed, declined, completed) as they happen. Downstream systems update CRM records or trigger follow-up workflows without polling. Annature emits per-event payloads with envelope and recipient identifiers so the agent can correlate against its source records.

Example prompt: Call POST /v1/webhook-endpoints with the listener URL and the desired event types, then verify a 2xx response and log the returned webhook ID

### AI Agent Signature Routing via Jentic

An AI agent that closes deals or onboards customers can route documents through Annature using Jentic without managing the X-Annature-Id key directly. Jentic's intent search routes the agent to POST /v1/envelopes with its full schema, and the API key is loaded from the vault at execution time so it never enters the agent's prompt or tool context.

Example prompt: Search Jentic for 'send a document for signature with Annature', load POST /v1/envelopes, and execute with the negotiated contract PDF and the customer's signing details

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/envelopes | Create a new signing envelope |
| POST | /v1/envelopes/{id}/send | Dispatch an envelope to its recipients |
| GET | /v1/envelopes/{id} | Retrieve envelope details and status |
| GET | /v1/envelopes/paged | List envelopes with pagination |
| POST | /v1/accounts/{id}/resend-verification | Resend the verification code to a recipient |
| GET | /v1/templates | List reusable envelope templates |
| POST | /v1/webhook-endpoints | Register a webhook URL for envelope events |

## Key resources

- **Envelopes** — Create, send, list, and retrieve envelopes; trigger sending and resend operations
- **Documents** — Manage the PDF documents attached to envelopes
- **Recipients** — Manage signers and viewers attached to envelopes
- **Templates** — Reusable envelope blueprints with pre-placed fields
- **Fields** — Signature, initial, and data fields placed on documents
- **Webhook Endpoints** — Register URLs to receive envelope event callbacks
- **Accounts** — User accounts within an Annature organisation
- **Organisations** — Tenant-level configuration for multi-team setups
- **Groups** — Permission and routing groups within an organisation

## Why Jentic

- **Setup:** Wiring the Annature API by hand means managing the X-Annature-Id key and sequencing envelope creation, sending, and status polling yourself. Through Jentic you install once, import Annature from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Annature puts the envelope id in the URL path (/envelopes/{id}/send, /envelopes/{id}), so a rule can pin your agent to one envelope: it can send and read that envelope and nothing else. You choose the operations it may call, so webhook-endpoint changes are not included unless you add them.
- **Credential handling:** Your Annature X-Annature-Id key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a document for signature' or 'check envelope status', and Jentic returns the matching Annature operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PandaDoc API** — PandaDoc covers similar e-signature and document workflow features with broader proposal tooling.
- **SignWell API** — SignWell offers e-signature with template, recipient, and webhook primitives comparable to Annature.
- **SignRequest API** — SignRequest provides envelope, signer, and template endpoints for digital signing.

## FAQ

### Why is there no official OpenAPI spec for Annature API?

Annature does not publish an OpenAPI specification - its docs live at docs.annature.com.au as Markdown reference. Jentic generates and maintains this spec so that AI agents and developers can call Annature via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Annature API use?

Annature uses an API key passed in the X-Annature-Id header. Keys are scoped per organisation. Through Jentic the key is stored in the encrypted vault and injected at execution time, so the raw key never enters the agent's prompt context.

### Can I send envelopes from a template with the Annature API?

Yes. Call GET /v1/templates to list available templates and POST /v1/envelopes referencing the template ID along with recipient details. This avoids re-uploading the underlying PDF for each send.

### What are the rate limits for the Annature API?

The OpenAPI spec does not declare explicit rate limits. Annature applies per-organisation throughput on the live service - back off on 429 responses and check your Annature account's plan tier for the exact ceiling before high-volume sending.

### How do I send a document for signature with Annature through Jentic?

Run pip install jentic, then search Jentic for 'send a document for signature with Annature'. Jentic returns POST /v1/envelopes with the recipient and document schema. Execute with your PDF and recipient list, then call POST /v1/envelopes/{id}/send to dispatch.

### Does the Annature API emit completion webhooks?

Yes. Register a webhook URL via POST /v1/webhook-endpoints and Annature emits per-event payloads when envelopes are sent, viewed, signed, declined, or completed, so downstream systems can update without polling.

### Can I limit what my agent is allowed to do with the Annature API?

Yes. Because you run Jentic One yourself, your own rules decide which Annature operations and credentials the agent may use. Since Annature puts the envelope id in the URL path, such as /v1/envelopes/{id}/send and /v1/envelopes/{id}, you can pin the agent to a single envelope so it can only send and read that one and nothing else. You also choose which operations it may call, so it cannot register or change webhook endpoints unless you explicitly allow that.