The Get Usage Charge List API is used to retrieve all usage charges associated with a specific recurring application charge. This API is helpful for tracking all usage charges within a billing cycle, providing insights into how the capped amount is utilized.
This API is especially useful for:
Viewing all usage charges for a recurring application charge.
Monitoring usage patterns to ensure the capped amount is not exceeded.
The amount already used in the current billing cycle.
"3.00"
usage_charges[].balance_remaining
string
The remaining balance available in the capped amount.
"7.00"
usage_charges[].created_at
string
Timestamp when the usage charge was created.
"2024-04-23T06:40:51Z"
Error Response
Error responses in the API can be represented using two different fields: errors and error. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.
Field
Type
Example
Description
errors
Array
["Record not found"]
A list of errors encountered during the request processing.
Field
Type
Example
Description
error
String
"page not found"
Indicates an error encountered during the process
Error Detail
Status Code
Message
Possible Reason
Example Response
400
Bad Request
Invalid input format or request structure (e.g., missing required fields or incorrect data types).
Bad Request
Unauthorized
The request is missing valid authentication credentials or the credentials provided are invalid.
Unauthorized
404
Not Found
The charge Id is not found.
"Record not found"
422
Unprocessable Entity
The charge Id is empty.
"PerPage is required"
API Structure Overview
Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!