Documentation
Guides to get running, and a reference generated from the same contract the service enforces.
There are two APIs. Most integrations need only the first.
Signing API
Section titled “Signing API”Have a person sign PDFs from your own app, including a person who holds no certificate yet: their certificate is issued when they accept. One secret key, test and live modes, webhooks.
| Guide | What it covers |
|---|---|
| Overview | How a signing request works, and the two keys. |
| Quick start | A document signed in test mode, in five calls. |
| Loan system guide | The server side of a loan signed in the bank’s app. |
| Banking app guide | Accept, Reject and the code, in Kotlin, Swift and Flutter. |
| API reference | Every operation and schema. |
Certificates API
Section titled “Certificates API”Manage the certificate lifecycle directly: enroll people, deliver credentials to their devices, suspend and revoke. It uses workload certificates and mutual TLS.
| Guide | What it covers |
|---|---|
| Sandbox quick start | From sign-up to a first API call, without contacting anyone. |
| Orientation | What the platform does, and where your workflow fits. |
| Concepts | Subscribers, enrollments, certificates and signatures. |
| Credentials | Workload certificates, private_key_jwt and mutual TLS. No client secret. |
| Webhooks and events | What is delivered, how it is signed, and how retries work. |
| Errors | Every error code and what to do about it. |
The certificates API reference lists every operation with its parameters, schemas and example requests. Import the same operations into Postman with the generated collection.