Your first signature
From an API key to a signed agreement in a few requests.
1. Create an account and API key
Use sandbox.bink.fi for testing and app.bink.fi for production. Create an API key in Settings → API. Copy it when it is created, and verify your account email before calling document endpoints. Keys inherit the access of their owning user.
2. Select your tenant
Call GET /api/tenants with X-Api-Key. Use the returned tenant id for document creation and listing. GET /api/tenants/{tenantId} returns your membership and role, not a tenant details object.
3. Upload an agreement
Use POST /api/documents/quick-create with multipart/form-data. Provide one file, tenantId, and signees as a JSON string containing an array of objects with email and name fields. Use a PDF and keep the file below 50 MiB. The response includes the new document id. Creation leaves the document in draft; it does not send invitations.
4. Send for signing
Call POST /api/documents/{documentId}/send-for-signing with no request body. This consumes signature credits and sends invitations according to the tenant’s email settings and document signing order. Inspect the per-recipient delivery results as well as the HTTP status.
5. Track completion
Subscribe to webhooks or retrieve the document. A signed document has completed sealing and exposes a short-lived download URL. Download URLs expire; retrieve the document again to obtain a fresh URL.