Get Recurring Application Charge

The Get Recurring Application Charge API is used to retrieve detailed information about a specific recurring application charge using its unique identifier (charge_id). This API helps developers verify the status, configuration, and metadata of a recurring charge associated with an application.

This API is especially useful for:

  1. Tracking the current status of a recurring charge (e.g., pending, active, cancelled).
  2. Viewing important charge metadata such as price, terms, and return_url.
  3. Auditing the lifecycle of a recurring application charge.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Path Parameters

ParameterTypeRequiredDescriptionExample
charge_idstringrequiredThe unique identifier of the recurring charge37222669345671159

Response Explanation

Public Response Parameters

📘

Public Response Parameters

Success Response

FieldTypeDescriptionExample
idstringThe unique ID of the recurring charge37222669345671159
application_idstringThe ID of the application associated with the charges1deCNxrHkePwO3HDZDb_zfwJAqe07nz
namestringThe name of the recurring application chargetest
pricestringThe price of the recurring application charge100
capped_amountstringThe capped amount for usage-based billing10
termsstringThe terms and conditions of the recurring application chargeterms
return_urlstringThe URL to which the user is redirected after paymenthttps://shoplazza.com
confirmation_urlstringThe URL where the user can confirm the chargehttps://test-shoplazza.stg.myshoplaza.com/a/confirm_url
statusstringThe current status of the charge (e.g., pending, active, cancelled)pending
trial_daysint32The number of trial days for the charge0
activated_onstringThe date when the charge was activatednull
trial_ends_onstringThe date when the trial period endsnull
billing_onstringThe date when billing startsnull
cancelled_onstringThe date when the charge was cancellednull
cancel_sub_onstringThe date when the subscription was cancellednull
testbooleanIndicates whether this is a test charge (true or false)false
created_atdatetimeThe date when the charge was created2024-04-23T06:26:46Z
updated_atdatetimeThe date when the charge was last updated2024-04-23T06:26:46Z

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
errorsArray[ "file number error"]A list of errors encountered during the request processing.
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
404Not FoundThe charge Id is not found or empty."Record not found"

API Structure Overview

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