Get Client Pendency by ID
GET/v1/crossborder/client-pendencies/:id
Retrieve a client pendency by its unique identifier, including its current item.
Request
Path Parameters
Client pendency ID.
Header Parameters
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
Responses
- 200
- 401
- 403
- 422
Client pendency returned successfully.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
Client pendency ID.
Client ID.
Possible values: [PENDING, IN_ANALYSIS, APPROVED, REJECTED]
Request status.
Possible values: [LOW, HIGH]
Request criticality.
Possible values: [IDENTITY_CARD, DRIVERS_LICENSE, PASSPORT, FOREIGNER_ID, MILITARY_ID, PROFESSIONAL_ID, WORK_CARD, BIRTH_CERTIFICATE, MARRIAGE_CERTIFICATE, SELFIE, SIGNATURE_CARD, PROOF_OF_ADDRESS, BANK_STATEMENT, PROOF_OF_INCOME, TAX_STATEMENT, ARTICLES_OF_ASSOCIATION, COMPANY_BYLAWS, INCORPORATION_STATEMENT, POWER_OF_ATTORNEY, LEGAL_STATEMENT, CONTRACT, INVOICE, SOURCE_OF_FUNDS_DECLARATION, PEP_DECLARATION, SANCTIONS_SCREENING_REPORT, OTHER]
Requested document type.
Possible values: [IDENTIFICATION, ADDRESS, FINANCIAL, CORPORATE, COMPLIANCE, OTHER]
Document category.
Compliance's comment on the current item.
Client's own comment on the current item.
Creation date.
Update date.
documents object[]required
Documents linked to this pendency current item, if any.
Client document ID.
Document name.
Document description.
Possible values: [IDENTITY, PROOF_OF_ADDRESS, BANK_STATEMENT, INVOICE, CONTRACT, OTHER]
Document type.
File ID.
Creation date.
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"client_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"status": "PENDING",
"criticality": "HIGH",
"document_type": "PASSPORT",
"document_category": "IDENTIFICATION",
"compliance_comment": "string",
"client_comment": "string",
"created_at": "2026-10-27T17:48:17.909Z",
"updated_at": "2026-10-27T17:48:17.909Z",
"documents": [
{
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"name": "Passport.pdf",
"description": "Passport front page",
"type": "IDENTITY",
"file_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"created_at": "2026-10-27T17:48:17.909Z"
}
]
}
User authentication failed.
- application/json
- Schema
- Example (from schema)
Schema
- any
{
"statusCode": 401,
"error": "USER",
"message": "Access is denied."
}
User access denied, or the authenticated wallet does not own the pendency.
- application/json
- Schema
- Example (from schema)
Schema
- any
{
"statusCode": 403,
"error": "FORBIDDEN",
"message": "Wallet does not own the requested client pendency."
}
If any required params are missing or have invalid format or type, or if the client pendency does not exist or was deleted.