Get a Document Context
GET/v4/documents/:documentId/context
This endpoint retrieves the context of a specific document.
Request
Path Parameters
The unique identifier of the document.
Responses
- 200
- 400
- 401
- 403
- 404
- 408
- 500
The retrieved document context.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
A unique string identifier for the document context.
The application identifier which is used to identify the application used.
Possible values: [DEVELOPMENT
, STAGING
, PRODUCTION
]
The execution environment of the application where request are executed.
An optional external identifier that can be used to reference the document context from external systems.
Possible values: [PDF
, PDF_ENCRYPTED
, FILE
, DATA_JSON
, DATA_XML
, PRIVATE_FILE
]
Represents the type of document that can be signed to the Ignisign application.
The name of the file associated with the document.
The size of the file associated with the document, typically in bytes.
A user-friendly label to identify the document.
A detailed, human-readable description of the document.
The MIME type of the file associated with the document, such as 'application/pdf' for PDF files.
The hash of the document.
Possible values: [CREATED
, PROVIDED
, ARCHIVED
]
Represents the current status of a document in the Ignisign application.
The unique identifier of the document request associated with this document.
The unique identifier of the signature request associated with the document.
The date and time when the document context was created, formatted as a string in ISO 8601 format.
statements
object[]
The statements related to the document.
A unique string identifier for the signature request statement.
The application identifier which is used to identify the application used.
Possible values: [DEVELOPMENT
, STAGING
, PRODUCTION
]
The execution environment of the application where request are executed.
The unique identifier of the signature request associated with this statement.
If target value is 'DOCUMENT', this value is unique identifier of the document associated with this statement.
Possible values: [SIGNATURE_REQUEST
, DOCUMENT
]
The target of the signature request statement. This can be 'SIGNATURE_REQUEST' or 'DOCUMENT'.
The label of the statement represented in MD format.
signatureSummaries
object[]
required
The signatures associated with the document context.
The unique identifier of the signature.
The unique identifier of the signer who provided the signature.
The date and time when the signature was realized, formatted as a string in ISO 8601 format.
{
"_id": "string",
"appId": "appId_XXXX-XXXX-XXXX-XXXX-XXXX",
"appEnv": "DEVELOPMENT",
"externalId": "string",
"documentNature": "PDF",
"fileName": "string",
"fileSize": 0,
"label": "string",
"description": "string",
"mimeType": "string",
"documentHash": "string",
"status": "CREATED",
"documentRequestId": "string",
"signatureRequestId": "string",
"_createdAt": "2024-07-29T15:51:28.071Z",
"statements": [
{
"_id": "string",
"appId": "appId_XXXX-XXXX-XXXX-XXXX-XXXX",
"appEnv": "DEVELOPMENT",
"signatureRequestId": "string",
"documentId": "string",
"target": "SIGNATURE_REQUEST",
"labelMd": "string"
}
],
"signatureSummaries": [
{
"signatureId": "string",
"signerId": "string",
"date": "2024-07-29T15:51:28.071Z"
}
]
}
Bad request error
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}
Unauthorized error
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}
Forbidden
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}
Not Found
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}
Timeout
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}
Internal Error
- application/json
- Schema
- Example (from schema)
Schema
The main message related to the error. It should provide an explanation or additional information about the error.
The timestamp when the error occurred, represented in UTC. It follows the format 'YYYY-MM-DD HH:mm:ss ZZ'.
The HTTP status code associated with the error. It indicates the status of the corresponding HTTP response.
The error code. It should be one of the IGNISIGN_ERROR_CODES (not linked here due to the high number of possible codes).
Additional contextual information related to the error. This object can contain any relevant properties.
{
"message": "string",
"timestamp": "2024-07-29T15:51:28.071Z",
"status": 0,
"code": "string",
"context": {}
}