Annature API

Name: Annature API API
Brand: Annature API
Availability: InStock

★ Only Publicly Available SpecProductivityCollaborationapiKey45 EndpointsREST

For 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.

Quickstart

Get started with Annature API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a document for signature with Annature"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Annature API API.

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

Manage account users, organisations, and groups for multi-team signing setups

GET STARTED

Start building with Annature API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to send a contract for digital signature through Annature, Create a signing envelope from an existing template, List all envelopes that are awaiting recipient signature, Retrieve the signed PDF for a completed envelope

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

Jentic publishes the only available OpenAPI specification for Annature API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Annature API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

45 endpoints — jentic publishes the only available openapi specification for annature api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Annature X-Annature-Id keys are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the raw API key never enters the agent's prompt or tool context, which matters because the key authorises sending legally binding envelopes.

Intent-based discovery

Agents search by intent (e.g., 'send a document for signature with Annature') and Jentic returns POST /v1/envelopes with its input schema, so the agent does not have to read Annature's recipient and field documentation manually.

Time to first call

Direct Annature integration: 1-2 days for auth, envelope creation, webhook handling, and signed-PDF retrieval. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PandaDoc API

PandaDoc covers similar e-signature and document workflow features with broader proposal tooling.

Choose PandaDoc when the agent also needs CPQ-style proposal generation alongside signature collection.

Alternative

SignWell API

SignWell offers e-signature with template, recipient, and webhook primitives comparable to Annature.

Choose SignWell when the agent operates outside Australia and prefers a US/EU-hosted e-signature provider.

Alternative

SignRequest API

SignRequest provides envelope, signer, and template endpoints for digital signing.

Choose SignRequest when the agent needs an EU-based provider with similar envelope semantics to Annature.

FAQs

Specific to using Annature API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.