Start free

Integrations & API

Contracts that send themselves when your business says so

A deal is marked won, a tenant is approved, a booking is confirmed: your system creates the agreement from a template and sends it, and hears back the moment it is signed. A REST API, signed webhooks and embedded signing, documented on one page.

Start free See plans
  • REST API with API keys and scopes
  • Signed webhooks with retries
  • Embedded signing

  • No copying and pasting between systems

    The names, emails and values your software already holds go straight into the contract. Nobody retypes a thing.

  • Your records update themselves

    When the contract is signed, your CRM or ledger finds out in seconds and moves the deal, the tenancy or the invoice along.

  • Signing inside your own product

    Customers sign without leaving your app, and your app knows when they have finished.

  • Keys you can trust and revoke

    Scoped API keys, HMAC-signed deliveries, rate limits and a delivery log, so the integration is safe to run unattended.

REST API

Create, send and track agreements from code Pro

JSON over HTTPS with an API key. Create a contract from a template or from files, add recipients and pre-filled values, send, poll status, download the sealed file and certificate.

Templates do the heavy lifting
Reference a template by ID and supply the people for each role plus field values. Fields, routing, identity methods and reminder defaults come from the template.
Scoped keys
contracts:read, contracts:write, templates:read. Create a key per integration, see when it was last used, revoke it in one click.
Predictable limits
Rate limits per key; clear error messages validated against a schema. The developer page has the endpoint list and examples.
Webhooks

Hear about every signature the moment it happens

Subscribe a URL to the events you care about: sent, viewed, signed, completed, declined, voided. Deliveries are signed with an HMAC and retried with back-off if your endpoint is down.

Verify it came from us
Each delivery carries a signature over the payload using a secret you hold. Reject anything that does not verify.
Retries and a log
Failed deliveries are retried on a schedule. Settings shows every delivery, its attempts and your endpoint's response code.
Idempotent by design
Each event has an ID, so a redelivery is easy to recognise and ignore.
Embedded signing

The signing page, inside your app

Open the signing URL in embedded mode in an iframe. When the signer finishes, your page receives a completion message. Allowed origins are set per API key.

Where it fits
A customer portal, an onboarding flow, a kiosk at reception, a booking confirmation page.
Same proof
Embedded signatures carry the same identity options, seal and certificate as any other. Identity and security.
Patterns

The three integrations most small businesses build

You rarely need more than one trigger and one webhook.

CRM: deal won → contract sent
Create from the service-agreement template with the deal's values; on "completed", move the deal to closed-won and attach the sealed file. For sales.
Lettings: applicant approved → tenancy pack sent
Create from the tenancy template with the property and rent; on "completed", mark the property let and start the deposit clock. For landlords and agents.
Practice management: new client → engagement letter
Create from the engagement-letter template; on "completed", open the client file and raise the first invoice. For finance.
Built for

Who gets the most from this

Works with

The rest of the product

Plans

Which plan you need

The API, webhooks and embedded signing are on Pro (£12 a month or £99 a year) and Team (£29 a month). Free accounts can create keys and test against the monthly contract limit. The API lives at https://api.airesdocs.com.

Compare the plans

Read next
Questions

Common questions about integrations & api

Anything missing? The help page has more, or email support and a person will reply within one business day.

What can I do with the API?

Create a contract from a template or from files, add recipients and pre-filled values, send it, check its status, download the finished file and certificate, list templates, and manage webhooks. Authentication is by API key with scopes; everything is JSON over HTTPS. The developer page describes the endpoints.

What events do webhooks deliver?

Sent, viewed, signed, completed, declined and voided. Each delivery is signed with an HMAC so you can check it came from us, and failed deliveries are retried with back-off. You can see every delivery and its response in Settings.

Can I put the signing page inside my own app?

Yes. Open the signing URL in embedded mode inside an iframe and listen for the completion message. Allowed origins are set per API key so only your sites can embed it.

Which integrations do you have?

AiresDocs connects to your systems through the API and webhooks rather than a catalogue of pre-built connectors. Most customers trigger a contract from their CRM, booking system or back office when something happens (a deal is won, a tenant is approved) and update their records when the webhook says it is signed. If you use an automation tool that speaks HTTP, it can drive AiresDocs.

Is there a sandbox?

Use a free account as your sandbox: create a key, send contracts to yourself, receive webhooks on a test URL. Nothing about the API differs between plans except that Free has the monthly contract limit.

How are API keys protected?

Keys are shown once and stored hashed. Each key has scopes (read contracts, write contracts, read templates), a prefix you can recognise in logs, a last-used time, and can be revoked instantly. Requests are rate-limited.

Read the developer page, then send a contract from code

Endpoints, authentication, webhook signing and embedded signing on one page. A free account is your sandbox.

Start free See plans