signdoc/pades
The signdoc/pades
API is used in the context of PAdES electronic signing. For a quick-start, please refer to our Getting started guide for electronic signing.
Overview
URL | https://<signdoc-baseurl>/signdoc/pades |
---|---|
Authorization | Access Token as Bearer Token in Authorization Header |
Upload sign order to SignDoc resource server
POST [signdoc-baseurl]/signdoc/pades
Request
Headers
Key | Value |
---|---|
Authorization | Bearer |
Content-Type | application/json |
Request body
Key | Type / Description | Example JSON | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| JSON object:
| "signProperties": { | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| JSON object:
| "padesSignProperties": { | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| JSON array of documents to be signed (minimum one). The document to be signed is represented as a JSON object:
Be aware that very large PDF files, typically files with a large number of images, might give a less than optimal user experience due to the document processing time. The total package size has no upper limit, but we recommend to keep the total size below 35MB. | "documents": [ "description": "My document", | ||||||||||||||||||||||||||||||||||||||||||||||||||||
(required) | JSON array of string. Must contain at either The string values will determine the content result when retrieving a completed sign order later:
| ["padesSignedPdf", "padesAppendix", "documentHash"] |
Example request
POST [signdoc-baseurl]/signdoc/pades { "signProperties": { |
Response
Content-Type: application/json
Code | Description | Example JSON response content |
---|---|---|
201 Created | Successfully uploaded PAdES sign order | { |
400 Bad request | Could not create order due to error in request. See the "errors"-array in the response for details. | { |
403 Forbidden | Access token is invalid. | AccessToken is invalid - Please provide reference: AbcDEf if reporting the problem. |
Response if pdfSpec
is used
Content-Type: application/json
Code | Description | Example JSON response content |
---|---|---|
201 Created | Successfully uploaded and converted PAdES sign order conversionWarnings contains an array of warnings that occurred during the conversion. Possible values are:
In CURRENT the response will always be DISABLED("PDF conversion is disabled") and "converted" = false | { |
400 Bad request | Could not convert order due to error in request. Documents that could not be converted will have a list of errors in conversionErrors. Possible conversionErrors are:
| { |
403 Forbidden | Access token is invalid. | AccessToken is invalid - Please provide reference: AbcDEf if reporting the problem. |
Check status of sign order
GET [signdoc-baseurl]/signdoc/pades
Request
Headers
Key | Value |
---|---|
Authorization | Bearer access_token |
Query parameters
Parameter | Type | Description |
---|---|---|
sign_id | string | The sign_id that was return when uploading the signing order. |
Example request
GET [signdoc-baseurl]/signdoc/pades?sign_id=4120de56-4391-4e5a-adea-a28e62daac7e |
Response
Code | Description | Example JSON response content |
---|---|---|
200 OK | Sign order was found. Returns the order state. Possible values are:
| { |
204 No Content | Sign order was not found. This could be caused by timeout or an invalid | (empty) |
400 Bad Request | The query parameter sign_id was not provided. | signId can not be empty - Please provide reference: AbcDEf if reporting the problem. |
403 Forbidden | Access token is invalid or missing. | AccessToken is invalid - Please provide reference: AbcDEf if reporting the problem. |
Delete sign order and download signing results
DELETE [signdoc-baseurl]/signdoc/pades
The sign order will be deleted if this request is made, regardless of sign order state.
Request
Headers
Key | Value |
---|---|
Authorization | Bearer access_token |
Query parameters
Parameter | Type | Description |
---|---|---|
sign_id | string | The sign_id that was return when uploading the signing order. |
Example request
DELETE [signdoc-baseurl]/signdoc/pades?sign_id=4120de56-4391-4e5a-adea-a28e62daac7e |
Response
Code | Description | Example JSON response content | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
200 OK | Sign order was found. The claims returned in the signing results depends on the values pass to the
If order is not completed, i.e. order state is not | { | |||||||||||||||||||||||||||
204 No Content | Sign order was not found. This could be caused by timeout or an invalid | (empty) | |||||||||||||||||||||||||||
400 Bad Request | The query parameter sign_id was not provided. | signId can not be empty - Please provide reference: AbcDEf if reporting the problem. | |||||||||||||||||||||||||||
403 Forbidden | Access token is invalid or missing. | AccessToken is invalid - Please provide reference: AbcDEf if reporting the problem. |