Get Signature Requests - Paginated
GET/v4/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
Array [
]
]
signatureRequests
object[]
required
An array of signature requests, each represented by an IgnisignSignatureRequest_WithDocName object.
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.
Possible values: [STANDARD
, SIGNER_SETUP
, SEAL
, SEAL_M2M
, BARE_SIGNATURE
]
The type of signature request. This parameter is used to define the type of signature request to be created. This will determine the type of signature request that will be created and the steps that will be required to complete the signature request.
The title of the signature request.
The description of the signature request.
Possible values: [EN
, FR
, DE
, ES
, IT
, PT
, NL
, PL
, JA
, KO
, AR
, HE
]
Represents the languages for signatures supported by a signature profile.
Possible values: [DRAFT
, WAITING_DOCUMENTS_GENERATION
, READY
, IN_PROGRESS
, COMPLETED
, EXPIRED
, FAILED
, CANCELLED
, PROCESSING
, CHILDREN_GENERATED
]
Represents the current status of a signature request in the Ignisign application.
a free field to store an identifier that can be used to link the signature request to an external system.
The id of the user who created the signature request if this has been made into the IgniSign User interface.
The ids of the documents that are linked to the signature request.
The ids of the signers that have been invited to sign the signature request.
The ids of the signers that have already signed the signature request.
The expiration date if the expirationDateIsActivated
parameter is true The action linked to this date is performed every 5 minutes, at 5, 10, 15... 55.
Indicates whether the expiration date is activated.
Possible values: [WHEN_READY
, SCHEDULED
]
Represents the diffusion mode of a signature request.
the diffusion date if diffusionMode
parameter is SCHEDULED
The action linked to this date is performed every 5 minutes, at 5, 10, 15... 55.
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
The version of the application environment settings used to create this signature request.
Possible values: [SIMPLE_STD
, ADVANCED_STD
, QUALIFIED_STD
]
Represents the method used for signatures in a signature requests in an Ignisign application.
signerProfilesUsed
object[]
Possible values: [SIMPLE_STD
, ADVANCED_STD
, QUALIFIED_STD
]
Represents the method used for signatures in a signature requests in an Ignisign application.
Indicates whether the signature request has been created with the individualizeRequests
option activated. If activated, each signer will receive a separate signature request. Approvers will be included in each signature requests.
Used only for M2M signature requests. The identifier of the M2M signature request. du not update directly this field.
The name of the first document that is linked to the signature request.
The label ( title ) of the first document that is linked to the signature request.
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",
"_createdAt": "2024-07-29T15:51:28.071Z",
"appId": "appId_XXXX-XXXX-XXXX-XXXX-XXXX",
"appEnv": "DEVELOPMENT",
"signatureRequestType": "STANDARD",
"title": "string",
"description": "string",
"language": "EN",
"status": "DRAFT",
"externalId": "string",
"creatorId": "string",
"documentIds": [
"string"
],
"signerIds": [
"string"
],
"signedBy": [
"string"
],
"expirationDate": "2024-07-29T15:51:28.071Z",
"expirationDateIsActivated": true,
"diffusionMode": "WHEN_READY",
"diffusionDate": "2024-07-29T15:51:28.071Z",
"initialSignatureRequestId": "string",
"signerIdsAsApprover": [
"string"
],
"recipients": [
"string"
],
"appEnvSettingVersion": 0,
"defaultSignatureMethod": "SIMPLE_STD",
"signerProfilesUsed": [
{
"signerProfileId": "string",
"signatureMethodRef": "SIMPLE_STD",
"version": 0,
"signerIds": [
"string"
]
}
],
"individualizeRequests": true,
"m2mId": "string",
"docFileName": "string",
"docLabel": "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": {}
}