Skip to main content
GET
Available in🇮🇳 India
Use this endpoint to fetch one stored file of an account: its type, name, format and size. Ask for a signed link to download it.
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 include_signed_url=true for a signed download link in url.
  • You see only the files you uploaded and the Aadhaar that Razorpay downloaded from the Central KYC Records Registry (CKYC). Any other file returns 404 with not_found.
  • 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.
string
required
The unique identifier of the file, as the upload or the list returned it. file_ followed by 14 letters or digits. For example, file_Qx7Lm2Kd9Tz4Ab.

Query Parameters

boolean
Adds a signed download link as url. Default: false.

Response Parameters

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
A signed link to download the file. Set only by Fetch One Document with include_signed_url=true. Otherwise null. It is also null when Razorpay could not create the 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_formatThe request has one of these problems:
  • The file_id is not file_ followed by 14 letters or digits.
  • include_signed_url is not true or false.
Solution: Correct the value named in error.field.
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: 404Reason: not_foundNo file with this ID is visible on the account. The file does not exist, was deleted or belongs to another account. Files that Razorpay holds for the account other than your uploads and the CKYC Aadhaar are not visible either. error.field is file_id.Solution: Check the file_id. Use an ID from Upload a Document or Fetch All Documents.
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