Settlements
Fetch All Settlements
Fetch All Settlements using Razorpay Settlements API.
GET
Use this endpoint to retrieve details of all settlements.
Query Parameters
integer
Unix timestamp (in seconds) from when settlements are to be fetched.
integer
Unix timestamp (in seconds) till when settlements are to be fetched.
integer
Number of settlement records to be fetched.
- Default value:
10. - Possible value:
1to100. - This can be used for pagination, in combination with
skip.
integer
Number of settlement records to be skipped.
- Default value:
0 - This can be used for pagination, in combination with
count.
Response Parameters
string
The unique identifier of the settlement transaction. For example,
setl_7IZKKI4Pnt2kEestring
Indicates the type of entity. Here, it is
settlement.integer
The amount to be settled (in the smallest unit of currency). For example, ₹500 will be
50000.string
Indicates the settlement states. Possible values:
createdprocessedfailed
integer
This is the total fee charged for processing all payments received from customers settled to you in this settlement transaction. In case of a normal settlement the fee charge will be
0.integer
The total tax, in currency subunits, charged on the fees collected to process all payments received from customers settled to you in this settlement transaction. In case of a normal settlement the tax charge will be
0.string
The Unique Transaction Reference (UTR) number available across banks, which can be used to track a particular settlement in your bank account. For example,
1597813219e1pq6w.integer
Unix timestamp at which the settlement transaction was created.
Errors
The API {key/secret} provided is invalid.
The API {key/secret} provided is invalid.
Code:
4xxThe API credentials passed in the API call differ from the ones generated on the Dashboard.Solution: The API keys must be active and entered correctly with no whitespace before or after.from must be between 946684800 and 4765046400.
from must be between 946684800 and 4765046400.
Code:
400The from UNIX timestamp is not between 946684800 and 4765046400.Solution: Use a valid UNIX timestamp between 946684800 and 4765046400.to must be between 946684800 and 4765046400.
to must be between 946684800 and 4765046400.
Code:
400The to UNIX timestamp is not between 946684800 and 4765046400.Solution: Use a valid UNIX timestamp between 946684800 and 4765046400.The count must be at least 1.
The count must be at least 1.
Code:
400The count passed is 0.Solution: Ensure that count is at least 1.count or skip must be a non-negative integer.
count or skip must be a non-negative integer.
Code:
400A negative value was passed for the count or skip query parameter. The API responds with count: must be no less than 0. or skip: must be no less than 0. respectively.Solution: Pass count as an integer between 1 and 100, and skip as an integer greater than or equal to 0.count, skip, from, or to must be a valid integer.
count, skip, from, or to must be a valid integer.
Code:
400A non-integer value (for example a string like abc, or a human-readable date like 2024-01-01) was passed for one of the pagination or range query parameters. The API responds with a message of the form <field>: strconv.Atoi: parsing "<value>": invalid syntax.Solution: Pass all four query parameters (count, skip, from, to) as integers. from and to must be UNIX-epoch seconds, not human-readable dates.