Twala Now Supports API Integrations: Send, Sign, and Timestamp From Your Own Software

Twala now supports API integrations. Any team can connect its own software to Twala: a CRM that sends a contract when a deal closes, an HR system that sends an offer letter the moment it is approved, or a website where customers sign without ever leaving the page. Signing, sealing, verification, and the blockchain anchor all run on Twala underneath.

It is the same platform Twala’s own users sign and notarize on, now open to the software around it.

What you can build

An integration starts on the new Apps page. Create an app, issue API keys, and your software can:

Send envelopes from PDFs or from your Twala templates, with recipients, roles, and fields, as drafts or sent right away. Send reminders, void, and read every envelope’s history.
Have people sign inside your own site or app. With embedded signing, a recipient signs on Twala’s signing page within your product, with no email from Twala and no Twala account, then returns to the page you choose.
Let your users prepare envelopes in your product. Embedded sending opens Twala’s envelope editor inside your site, on your draft, so your users place fields and send without switching tools.
Hear about every change. Webhooks tell your server when an envelope is sent, a recipient opens or signs it, it is completed, voided, or declined, and when its hashes are anchored on the blockchain. Every delivery is signed and logged, and you can resend any of them.
Timestamp documents. Any app can timestamp documents through the API, sealed and anchored, on any plan.

Test first, for free

Every app has two kinds of keys. A test key sends envelopes that are free, go only to you or your team, carry a “Test — not legally binding” watermark on every page, and are never anchored. Build and demo as much as you like, up to 50 test envelopes per app a day, without spending anything.

A live key sends legally binding envelopes and timestamps. Live keys need a verified identity: your own identity verification for a personal app, or your team’s organization verification for a team’s app.

Pay for what you send

Live sending spends API credits: one credit for each envelope a live key sends, and one for each document it timestamps. Credits are bought in packages, held by your account or your team, shared by all its apps, and they never expire. Test mode never uses them. The Apps page shows your balance, and Credits history lists every purchase and every envelope or timestamp they paid for.

Docs your developers, and their AI tools, can read

The new developer guide covers it all: a quickstart that sends your first test envelope, guides for authentication, webhooks, embedded signing, timestamps, errors, and going live, and an API reference you can try from your browser, with every request shown in cURL, JavaScript, Python, PHP, Go, Java, C#, and Ruby.

Download the API’s OpenAPI document to import every endpoint into Postman, Hoppscotch, Insomnia, or Bruno. Every guide copies as Markdown, and the docs are published as llms.txt, so an AI coding assistant can read the same reference your developers do.

Built to be accountable

An app sends as one person, its sender, so every envelope it sends is that person’s and every email names them. On the envelope’s Activity, an embedded signer’s visit reads as opened through your app, and the Signing Certificate records that your app authenticated them. Team members who aren’t owners or admins never see a team’s apps, keys, or credits.

For resellers and system integrators

If you bring software to other organizations, the API is how Twala reaches them. Resellers can offer Twala alongside what they already sell, and system integrators can connect it to their clients’ CRM, HR, ERP, and case management systems. See resellers and system integrators, or talk to us about working together.

Getting started

Sign in to Twala, open Apps under Resources, and click Create app.
In the app’s details, click Create key and choose Test. Copy the key: it is shown only once.
Follow the developer guide’s quickstart to send your first test envelope.
Add a webhook endpoint, then create a live key and buy API credits when you are ready to go live.

Apps are open to anyone not on a team, and to a team’s owners and admins. To connect an AI assistant to your own account instead, see AI connectors.