Bring Twala to your customers. Resell it, or build it in.
Twala now supports API integrations. Resellers offer Twala alongside what they already sell, and system integrators and software makers connect it to the systems their clients run, with signing, sealing, and verification handled by Twala.
The Twala API: one request creates and sends an envelope from a template, and the app’s webhook endpoint then receives each event as it happens, from envelope.sent through recipient.completed and envelope.completed to envelope.anchored, each delivered with a 200 answer.
Three ways to work with Twala
Every arrangement is agreed with each partner. Tell us about your customers, and we’ll find the one that fits.
Resellers
Offer Twala’s eSignature, eNotary, and document AI to your customers under a reseller agreement, alongside the hardware, software, and services you already sell.
System integrators
Connect Twala to your clients’ CRM, HR, ERP, and case management systems, so documents go out for signature and come back sealed without anyone leaving the tools they use.
Software makers
Put legally binding signing inside your own product. Your users sign and send in your app, and Twala seals, verifies, and anchors every document underneath.
Everything a signing integration needs, in one REST API
Create an app on the Apps page, issue keys in test and live modes, add webhook endpoints, and send your first test envelope from the developer guide’s quickstart.
Envelopes and templates
Create envelopes from PDFs or your templates, add recipients and fields, send, remind, correct, void, and read every envelope’s history.
Embedded signing
People sign inside your website or app, with no email from Twala and no Twala account, and come back to the page you choose.
Embedded sending
Open Twala’s envelope editor in your own site, on your draft, for your user to place fields and send.
Webhooks
Signed HTTPS events when an envelope is sent, opened, signed, declined, completed, or anchored, with retries and a delivery log.
Timestamps
Timestamp documents through the API, sealed and anchored on a blockchain, on any plan.
AI connectors
Your customers can also connect the AI assistants they already use to their Twala accounts, on every plan, at no extra charge.
Docs your team, and its AI tools, can read
Guides with complete examples, an API reference you can try from the browser, and the request in eight languages. The reference is read from the API itself, so it always matches it.
- cURL, JavaScript, Python, PHP, Go, Java, C#, and Ruby
- An OpenAPI document for Postman, Hoppscotch, Insomnia, or Bruno
- llms.txt and a Building with AI agents guide for coding assistants
- Test mode: free, watermarked, never legally binding
Connecting an AI tool: Twala’s Connect to your Twala account page names the tool and the account it will act as, lists what it will be able to do, and says it never signs for anyone. After Connect, the tool is listed in AI connectors with its access, when it was connected and last used, and Disconnect.
From first call to live customers
Talk to us
Tell us about your customers and what you want to build or resell. We agree the terms that fit, and help you plan the integration.
Build in test mode
Create an app on the Apps page and a test key. Test envelopes are free, watermarked, and never legally binding, so you can build and demo without spending anything.
Go live
Verify your identity, or your organization for a team’s app, to create live keys. Live envelopes and timestamps spend API credits, which never expire.
Launch with your customers
Signing, sealing, verification, and the blockchain anchor run on Twala, built on a Supreme Court-accredited Electronic Notarization Facility.
Supreme Court of the PhilippinesAccredited ENF
Integrated Bar of the PhilippinesOfficial Partner
Department of Science & TechnologyGrant Recipient
Cloud Signature ConsortiumOfficial Member
Frequently asked questions
Plans, credits, embedded signing, and webhooks. Read the API announcement for more.
Do I need a Twala plan to use the API?
No plan includes API credits, and any account can create apps: someone on no team, or a team’s owners and admins. Live sending spends API credits, bought in packages; test mode is free.
What does a live API call cost?
One API credit for each envelope a live key sends, and one for each document it timestamps. Reading, listing, and webhooks spend nothing. Talk to us about credit packages for your customers.
Can my customers sign without a Twala account?
Yes. With embedded signing, a recipient signs inside your site or app, with no Twala account and no email from Twala. The signed document carries “Authenticated by” your app on its Signing Certificate.
How do I know a webhook came from Twala?
Every delivery is signed with the endpoint’s signing secret, and the developer guide shows how to check the signature. Each endpoint keeps a delivery log, and you can resend any delivery.
Can an AI coding assistant read the docs?
Yes. Every guide and endpoint copies as Markdown, the docs are published as llms.txt and llms-full.txt, and the OpenAPI document imports into Postman, Hoppscotch, Insomnia, or Bruno.
Who owns the customer relationship?
That depends on the agreement we make with you. Talk to us about reselling, referral, and integration arrangements.
Let’s build the future of documents, together.
Talk to us about reselling Twala or integrating it for your clients.