What is available, what is coming, what is not (for now)
One page that says it plainly, so you do not find out after you have started. Three lists: what works today, what is coming, and what is not available for now with what to do instead. If something in the third list is what you need, tell us: it is how we decide what comes next.
Available today
| Area | What works |
|---|---|
| Composer Fly documents from data |
Word, HTML and Excel templates to PDF, with versions; PDF/A, password and watermark;
validate before you pay; test calls that cost nothing;
bulk from JSON or CSV with one ZIP of results;
conversion of Carbone and Docmosis templates;
composing without keeping anything (dataless); idempotent calls; stable error codes. |
| Signer Fly e-signature |
Simple electronic signature (SES) with signing order, reminders, a signature placed by a tag in the document, the signer's page in Italian or English, a certificate and event trail as evidence, qualified seal and timestamp, text-message codes, and webhooks to your own system. |
| Document Fly one call |
Compose and send for signature in one request (how), alone or in bulk. |
| The platform | Several API keys with scopes and an expiry, an address allow-list you can set, two-factor sign-in to the console,
an audit trail you can export, and a public guide, /openapi.json and
/llms-full.txt for an AI agent. |
| Italian and English | The site, the legal texts (the Italian prevails), the console, the guide, every e-mail and text message and the signing pages, each in the reader's language; signers in the language you choose per envelope or per signer. The API answers in English. |
Coming soon
| What | Meanwhile |
|---|---|
| Advanced and qualified electronic signatures (AES and QES) | The API already accepts the level and refuses it with SIGNATURE_LEVEL_UNAVAILABLE until it is
ready, so nothing is approximated. You sign at SES, optionally sealed and time-stamped
(signature levels). The provider is not named yet and there is no date. |
Not available for now
These do not exist today and we are not promising a date. Each has a way round.
| Not available | What to do instead |
|---|---|
| Signing inside your own app (embedded signing) | The signer receives a link by e-mail or text message and signs on our page, which carries your branding.
A request that names DocuSign's clientUserId is refused with a message that says so. |
| Single sign-on (SAML, OpenID) for the console | Every person signs in with their own e-mail, a password and a second factor. The API is not affected: it uses keys. |
| Client certificates (mTLS) on the API | Scoped keys that expire, plus an address allow-list for your servers. |
| Official libraries (an SDK per language) | One endpoint is a small thing to call by hand: examples in nine languages,
or generate a typed client from /openapi.json. |
| A form in the console to make a document without any call | Make, Zapier or n8n with one HTTP step: how. |
| An MCP server for AI agents | Give your agent /llms-full.txt: integrating with an AI agent. |
Limits and what happens to your documents: Limits and retention.
How fast support answers: the FAQ. Whether everything works right now:
the status page (/status.json for a monitor).