Get Application Charge List

The Get Application Charge List API retrieves a paginated list of application charges associated with the current store. This allows developers to view and filter application charges based on specific criteria.

This API is especially useful for:

  1. Retrieving all application charges for auditing and analysis.
  2. Filtering charges based on their status or creation time.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Query Parameters

ParameterTypeRequiredDescriptionExample
per_pageint32NoLimit per page. Defaults to 20. Maximum value is 250.20
since_idstringNoRestrict results to after the specified ID.372212374292312759
charges_statusstringNoFilter charges by their statuses, separated by commas (e.g., pending, accepted, declined, etc.).pending,accepted,declined,active,expired<br>frozen,cancelled,paid_failed,paying

Response Explanation

Public Response Parameters

📘

Public Response Parameters

Success Response

FieldTypeDescriptionExample
countintTotal number of application charges returned.8
application_chargesarrayA list of application charges.
application_charges[].idstringThe unique ID of the application charge.372212374292312759
application_charges[].namestringThe name of recurring application charge.test
application_charges[].pricestringThe price of the application charge.10.0
application_charges[].confirm_urlstringThe confirmation URL for the application charge.https://test-shoplazza.stg.myshoplaza.com
application_charges[].return_urlstringThe redirect URL after payment.https://shoplazza.com
application_charges[].statusstringThe current status of the application charge.active
application_charges[].testbooleanWhether this is a test charge.false
application_charges[].created_atstringThe creation timestamp of the application charge.2024-04-23T02:39:05Z
application_charges[].updated_atstringThe last updated timestamp of the application charge.2024-04-23T02:39:19Z

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.

FieldTypeExampleDescription
errorString "page not found"Indicates an error encountered during the process

Error Detail

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized

API Structure Overview

Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!