Authorizations
An API key that grants access to the Connect API. You can create and manage API keys in the portal.
Headers
A unique key to ensure idempotency of requests. If a request with the same key has already been processed, the same result will be returned. The key must be unique for each distinct operation. Keys are expired after 24 hours, but we recommend using a new key for each request.
Modified requests with the same idempotency keys are rejected with a 409 Conflict
status code.
256
Path Parameters
The unique identifier for the signing session.
Response
Signing session cancelled successfully.
A contract signing session for an order requiring legal signature.
The unique identifier for this signing session.
"f7d2295f-0dd4-4ebe-8ec5-de2d0f41be7e"
The order that requires signing.
"44567801-a504-4f09-8089-31ea78bc239b"
The current status of a signing session.
PENDING
, IN_PROGRESS
, COMPLETED
, FAILED
, EXPIRED
, CANCELLED
Information about the person signing the contract.
The specific fields required depend on the signing provider. Use GET /signing/providers to discover which fields are required for each provider.
{
"name": "John Doe",
"email": "john.doe@example.com",
"identity": "199001011234"
}
When the signing session was created.
"2024-01-15T10:00:00Z"
The signing provider used for this session.
"bankid"
The language used for the signing interface.
"en"
The URL where the user should be redirected to complete signing.
"https://sign.provider.com/session/abc123"
The URL where the user will be redirected after signing completion.
"https://yourapp.com/orders/123/complete"
Download URL for the signed contract. Only available when status is COMPLETED.
"https://api.yourapp.com/documents/signed-contract-123.pdf"
When the signing was completed. Only present when status is COMPLETED.
"2024-01-15T14:30:00Z"
When this signing session expires.
"2024-01-15T23:59:59Z"
The reason for signing failure. Only present when status is FAILED.
"User cancelled signing process"
Additional metadata for the signing session.
{
"contract_type": "postpaid_subscription",
"customer_segment": "b2b"
}