Krebit Sign API
Use the API to prepare agreements, send them to recipients, and bring signed documents and contract values back into your application.
The workflow is the same whether you upload a PDF or create a contract from a template:
Authenticate → Create a draft → Add a PDF or contract → Add recipients → Send → Retrieve results
Start here
- Authenticate — connect your application and obtain an access token.
- Choose the document workflow that fits your integration:
- Send a PDF when your application already produces the document.
- Create a contract from a template when Krebit Sign should hold the template and collect field values.
- Handle completion events — receive a webhook, download the signed PDF, and retrieve contract values when applicable.
Both walkthroughs use cURL and jq, the same environment variables, and a single recipient. Each can be followed independently after authentication.
The main concepts
| Concept | What it represents |
|---|---|
| Signing | The package that holds documents or contracts, recipients, and sending status. |
| Document | A PDF uploaded by your application or generated from a contract. |
| Template | A reusable contract layout created in Krebit Sign. |
| Contract | A copy of a template whose fields can be prefilled and completed before signing. |
| Recipient | A person asked to sign or approve. This is separate from the user who authorized your API connection. |
A signing can contain multiple documents or contracts. The signing lifecycle guide explains recipient order, draft editing, reminders, and completion.
Find the details you need
- API reference — request and response schemas, pagination, and errors.
- Connected user — check which account authorized the connection.
- AI integration prompts — optional prompts for building against these same guides and schemas.
All API requests use your organization's domain, such as https://yourco.krebit.se. Start with authentication to set up the connection.