Every operation in SIGN PT consists of an INTENTION and a TRANSACTION record. The compliance data needed on the printed document (ATCUD, QR code and signature) is only returned once the record is COMPLETED.
Only print or hand over the document after the record is COMPLETED.
What to do after each response
| Situation | Meaning | What to do |
|---|---|---|
| 400 response | No record was created | Resend the request with a different idempotency key |
| 500 response | Un unexpected error has occurred | Check if the record was created before retrying with a different idempotency key. |
200 response, later REJECTED or FAILED | The record has no compliance data. The number is not consumed | Create a new INTENTION and a new record. Do not hand over the document |
| Timeout, no response | The outcome is unknown | Follow the recovery steps below |
Idempotency
- Use a unique
X-Idempotency-Keyfor every new request. - Within 24 hours, sending the same key with the same payload returns the cached response, with
X-Idempotency-Replayed: true. No second submission is made. - The same key with a different payload returns a 422 error.
- After 24 hours, the key is treated as new. Query the record status with the INTENTION ID using the GET endpoint. If the record was not registered, resubmit with a new key.
Monitoring and volume
- There are no webhooks. A record in a final state (
COMPLETED,FAILEDorREJECTED) does not change, so there is no need to keep polling it. - For bulk sending, for example a backlog after an outage, we recommend about 5 invoices per second. Higher bursts can cause timeouts.