Request a limit increase
This endpoint creates a limit-increase request for a customer. Upload the supporting document first with POST /customers//documents and pass the returned documentId as supportingDocumentId. Each request raises the limits of one transaction type (type), and approval changes only that type’s limits. A customer can have one pending request per type; creating a second pending request for the same type returns 409 with code LIMIT_REQUEST_ALREADY_PENDING.
Authorizations
Bearer authentication header on the format Bearer <API_KEY>.
Headers
Optional UUID v4 idempotency key. If you resend the same key with a different request body, the API returns a 409 error. Cached responses include the header X-Idempotency-Cached: true. Keys expire after 24 hours.
Path Parameters
Customer's unique identifier.
Body
Transaction type whose limits the request raises. Approval changes only this type's limits. Each type can have one pending request at a time.
ONRAMP, OFFRAMP, TRANSFER "OFFRAMP"
documentId returned by POST /customers/{id}/documents for the uploaded supporting document.
"9d1e2f3a-4b5c-6d7e-8f90-1a2b3c4d5e6f"
Response
Resource successfully created.
Limit request's unique identifier.
"b2e1a2d4-1234-4a3b-9c4d-5e6f7a8b9c0d"
Customer's unique identifier.
"3c90c3cc-0d44-4b50-8888-8dd25736052a"
Transaction type whose limits the request raises. Null for requests created before limits were split by transaction type.
ONRAMP, OFFRAMP, TRANSFER, null "OFFRAMP"
Limits requested by the customer.
Limits approved by compliance. Each value is null until reviewed.
"LIMIT_REQUEST_BANK_STATEMENT"
"9d1e2f3a-4b5c-6d7e-8f90-1a2b3c4d5e6f"
Current status of the limit request.
IN_REVIEW, APPROVED, PARTIALLY_APPROVED, REJECTED "IN_REVIEW"
Compliance's comment. Set when rejected or partially approved.
null
"2024-01-15T10:00:00Z"
Also the review timestamp once the request leaves IN_REVIEW.
"2024-01-15T10:00:00Z"