Skip to main content
GET
Available in🇮🇳 India
Use this endpoint to fetch the stored files of an account, newest first. Filter by document type if you need one type only.
Handy Tips
  • Authenticate with the key and secret of your test pair or live pair. In the API playground, enter the test key as the username and its secret as the password. Use the live pair in live mode.
  • Pass type to return one document type. No match returns 200 with count as 0.
  • The list has no pagination. It returns every file you can see.
  • url is always null in the list. Fetch one document for its download link.
  • You see only the files you uploaded and the Aadhaar that Razorpay downloaded from the Central KYC Records Registry (CKYC). Other files never appear.
  • Responses carry Cache-Control: private, no-store. Do not cache them.

Path Parameters

string
required
The unique identifier of the account, acc_-prefixed. For example, acc_TcdGEzmfKQzEl1.

Query Parameters

string
Return only files of this document type. Default: all types. Know more about document types.

Response Parameters

string
Always collection.
integer
Number of files in items.
array
The files, newest first. Each has the parameters below.
string
Unique identifier for the file, file_ followed by 14 letters or digits.
string
Always document.
string
The document type of the file. Know more about the document types.
string
Always null in the list. Fetch one file with include_signed_url=true for its link.
object
About the stored file.
string
Where the file came from. Possible values:
  • upload: You uploaded it.
  • ckyc: Razorpay downloaded it from the CKYC record.
string
The file name as you sent it.
string
The format Razorpay detected from the file content, such as image/jpeg. It can be null.
integer
File size in bytes. It can be null.

Errors

Code: 400Reason: invalid_optiontype is not a supported document type.Solution: Send a supported document type. Know more about document types.
Code: 401Reason: invalid_credentialsThe Authorization header is missing or is not Basic. Other causes are a key that is not a partner key or a wrong secret. A secret also stops working when it is revoked or its rotation window ends.Solution: Send your partner key and secret as HTTP Basic credentials. Check that the secret is current for the key.
Code: 403Reason: onboarding_not_enabledYour app does not have access to the Onboarding APIs in this mode. Razorpay may also have turned off your app’s access.Solution: Contact Razorpay to get access to the Onboarding APIs for your app in this mode.
Code: 403Reason: ip_not_allowedThe request came from an IP address outside your app’s allowlist for its mode. Test mode checks the allowlist once it has an entry.Solution: Send requests from an IP range on your app’s allowlist for this mode. To use another range, add it to the allowlist on the Partner Dashboard.
Code: 403Reason: consent_withdrawnThrough Razorpay, the sub-merchant withdrew your permission to act on the account. Calls on this account never succeed again for your platform.Solution: Stop calling this account and update your records.
Code: 404Reason: not_foundNo account with this ID is mapped to your app in this mode. The account does not exist, belongs to another platform or belongs to a direct Razorpay merchant. It can also be a test account called in live mode.Solution: Check the ID in error.field. Use the ID of an account mapped to your app, in the same mode as your key.
Code: 429Reason: rate_limitedYour app sent more requests than its rate limit allows.Solution: Wait for the time in the Retry-After header, then retry.
Code: 500Reason: internal_errorSomething went wrong inside Razorpay.Solution: Retry the request.
Last modified on November 18, 2026