---
title: API and SDKs
description: Send documents from your own code with a REST API and typed clients for JavaScript and Python. The deeper guide is on the Developers pages.
---

# API and SDKs

Send documents from your own code with a REST API and typed clients for JavaScript and Python. The deeper guide is on the Developers pages.

## What you can do

Create a template from HTML or a file, send it to people with their roles, follow its state, remind or void it, download the signed PDF and its audit log, read reports, and start an embedded signing session. Sending is idempotent: repeating a request with the same Idempotency-Key returns the first answer.

## Clients

The JavaScript and TypeScript client and the Python client wrap every operation and verify webhook signatures. Both are MIT licensed. There are also an MCP server and agent skills so an AI assistant can send and track documents with a key that has limited scopes.

## Keys and scopes

Keys are made in Settings. A test key makes practice documents that are emailed only to you; a live key emails the people you send to. Scopes limit what a key can read or write, and a key can be revoked at any time.

## Go deeper

The Developers pages hold the quickstart, the API reference, the webhook guide, the SDK guides and the AI tools. This page is the short version.

## Five lines to send a document

With a key and a template id, sending is one call: the template, the people and their seats. The answer is the document's id and state, and how many signing emails went out. Poll the document, or let a signed webhook tell you when it is signed, then download the sealed PDF.

## Clients that do the boring parts

The JavaScript and Python clients retry safely, add an Idempotency-Key for you, walk through pages of results and check webhook signatures in a few lines. They are MIT licensed, so you can put them in any application.

## Where to go next

The Developers pages have the quickstart, the full reference generated from the same file the API publishes, the webhook guide, the SDK guides and the AI tools. Keys, scopes and test mode are explained on the authentication page.

## What a first integration looks like

Most teams start by creating a test key, sending one practice document to themselves and reading the answer. Next they add the webhook endpoint that tells their system when a document is signed, then switch to a live key. Nothing in that path needs a call with anyone, and the test key never emails the people you name.

## Questions people ask

**Is the API in every plan?**

Yes, within your monthly allowance.

**Can I try it without sending real email?**

Yes. A test key makes practice documents that are emailed only to you.

**Is there a file I can load into other tools?**

Yes, the OpenAPI file, and a Postman collection made from it.

## Keep reading

- [Developers](/developers)
- [API reference](/developers/api)
- [SDKs](/developers/sdks)
- [Embedding](/product/embedding)
- [Text tags and HTML](/product/text-tags)