Get Signature Requests - Paginated
GET/v3/applications/:appId/envs/:appEnv/signature-requests
This endpoint retrieves all signature requests for a given application and environment.
Request
Path Parameters
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.
Query Parameters
The page number to return.
Responses
- 200
- 400
- 401
- 403
- 404
- 408
- 500
Paginated signature requests.
- application/json
- Schema
- Example (from schema)
Schema
Array [
- WHEN_READY : The signature request will be sent to the signer as soon it is ready to be signed. This is the default value.
I.E: If there are no document request, the signature request will be sent to the signer as soon as the signature request is PUBLISHED.
If there are document request, the signature request will be sent to the signer as soon as all the document request are have been completed. - SCHEDULED : The signature request will be sent to the signer at a specific date. This date is specified in the diffusionDate field
]
signatureRequests
object[]
required
An array of signature requests, each represented by an IgnisignSignatureRequest_WithDocName object.
The unique identifier of the signature request.
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 identifier of the signature profile associated with the signature request.
The title of the signature request.
The description or details about the signature request.
The expiration date of the signature request.
Indicates whether the expiration date is activated for the signature request.
Possible values: [DRAFT
, WAITING_DOCUMENTS
, WAITING_DOCUMENTS_GENERATION
, READY
, IN_PROGRESS
, COMPLETED
, EXPIRED
, FAILED
, CANCELLED
, PROCESSING
]
Represents the current status of a signature request in the Ignisign application.
Possible values: [EN
, FR
, DE
]
Represents the languages for signatures supported by a signature profile.
An array of document identifiers associated with the signature request.
An optional external identifier that can be used to reference the signature request from external systems.
Possible values: [WHEN_READY
, SCHEDULED
]
Represents the diffusion mode of a signature request.
The date when the signature request is to be diffused.
An array of signer identifiers associated with the signature request.
An array of identifiers of the signers who have signed the signature request.
The date and time when the signature request was created.
The unique identifier of the user who created the signature request.
The name of the document associated with the signature request.
The label or title of the document associated with the signature request.
If the signature request has been created from a signature profile with the individualizeRequests
option activated, this field will contain the identifier of the initial signature request which it has been generated.
the ids of signers that will be approvers
the emails of signers that will receive a copy of the signed document
paginationData
object
required
The pagination data for the list of signature requests.
The total number of signature requests.
The current page number in the pagination.
The number of signature request events per page.
{
"signatureRequests": [
{
"_id": "string",
"appId": "appId_XXXX-XXXX-XXXX-XXXX-XXXX",
"appEnv": "DEVELOPMENT",
"signatureProfileId": "string",
"title": "string",
"description": "string",
"expirationDate": "2024-07-29T15:51:28.071Z",
"expirationDateIsActivated": true,
"status": "DRAFT",
"language": "EN",
"documentIds": [
"string"
],
"externalId": "string",
"diffusionMode": "WHEN_READY",
"diffusionDate": "2024-07-29T15:51:28.071Z",
"signerIds": [
"string"
],
"signedBy": [
"string"
],
"_createdAt": "2024-07-29T15:51:28.071Z",
"creatorId": "string",
"docFileName": "string",
"docLabel": "string",
"initialSignatureRequestId": "string",
"signersAsApprover": [
"string"
],
"recipients": [
"string"
]
}
],
"paginationData": {
"total": 0,
"page": 0,
"nbEventsPerPage": 0
}
}
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": {}
}