List the signatures of a request
/signature-requests/{signature_request_id}/signaturesLists the live signatures of one request, newest first; the same answer as GET /signatures?filter[signature_request_id]=. 404 for an unknown request or one whose document the caller cannot read. Investors and advisors see only their own signatures. Ip address, user agent and hashes are not exposed; the signed PDF is signed_document_id, downloadable with GET /documents/{documentId}/download. Changes nothing.
Path parameters
The signature request's id.
Query parameters
- Default:
Page size (1–100). Defaults to 25; values are clamped to the range.
25 Opaque pagination cursor taken from a prior response's
meta.next_cursor.Comma-separated top-level fields to return.
idis always returned.Comma-separated fields to sort by: created_at. Prefix a field with
-for descending. Defaults to-created_at. The id is always the final tiebreak.Signatures of this request. Takes
[in]and[not_in]with a comma-separated list.Signatures on requests to have this document signed. Takes
[in]and[not_in]with a comma-separated list.Signatures to be given by this user or group id. Takes
[in]and[not_in]with a comma-separated list.- One of:
Signatures to be given by a signatory of this kind: user, group, multi_user or machine. Takes
[in]and[not_in]with a comma-separated list.user,group,multi_user,machine - One of:
Signatures in this status: pending, signed, verified, rejected, not_required, not_initialised, initialising, declined, withdrawn or error.
not_initialisedalso matches a signature with no status. Takes[in]and[not_in]with a comma-separated list.pending,signed,verified,rejected,not_required,not_initialised,initialising,declined,withdrawn,error Signatures on requests made on a folder in this folder's subtree, or on a document in it. Takes
[in]and[not_in]with a comma-separated list of at most 50 folder ids.Created at or after / before a UTC date-time such as 2026-03-01T00:00:00Z. Use
[gt],[gte],[lt]or[lte].
Responses
{
"data": [
{
"id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"signature_request_id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"document_id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"status": "pending",
"signatory": {
"id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"type": "user"
},
"signatory_name": "string",
"signed_document_id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"signed_using_method": "string",
"signing_methods": [
"string"
],
"captured_at": "2026-06-12T10:00:00+00:00",
"reason": "string",
"error": "string",
"created_at": "2026-06-12T10:00:00+00:00",
"updated_at": "2026-06-12T10:00:00+00:00"
}
],
"meta": {
"limit": 1,
"next_cursor": "string",
"prev_cursor": "string"
}
}Authorization failed. error.code is one of org_disabled,
ip_blocked, missing_scope, scope_disabled, user_disabled.
The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per
problem, or a code documented on the operation.
Examples
curl https://your-org-domain/kong/core/api/v2/signature-requests/{signature_request_id}/signatures\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"