GET /transactions
Lists all the transactions.
Servers
- {protocol}://{site}.{environment}:{port}/api/v2
- {protocol}://{site}-test.{environment}:{port}/api/v2
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
chargebee-request-origin-device |
String | No |
The device from which the customer has made the request |
chargebee-business-entity-id |
String | No |
If the site has multiple business entities, you can use this custom HTTP header to specify the business entity for which Chargebee should perform the operation. |
chargebee-request-origin-user |
String | No |
The email address of your customer/user. Use this when the email address has only ASCII characters. |
chargebee-request-origin-ip |
String | No |
The IP address of the customer where the request originated |
chargebee-request-origin-user-encoded |
String | No |
The Base64-encoded email address of your customer/user. Use this if the email address has UTF-8 characters. When this header is provided, the header chargebee-request-origin-user is ignored. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
reference_number |
Object | No |
optional, string filter The reference number for this transaction. For example, the check number when Example → reference_number[is] = "cus_u239732" |
gateway |
Object | No |
optional, enumerated string filter Gateway through which this transaction was done. Applicable only for 'Card' Payment Method. Possible values are : chargebee, chargebee_payments, stripe, wepay, braintree, authorize_net, paypal_pro, pin, eway, eway_rapid, worldpay, balanced_payments, beanstream, bluepay, elavon, first_data_global, hdfc, migs, nmi, ogone, paymill, paypal_payflow_pro, sage_pay, tco, wirecard, amazon_payments, paypal_express_checkout, gocardless, adyen, orbital, moneris_us, moneris, bluesnap, cybersource, vantiv, checkout_com, paypal, ingenico_direct, exact, mollie, quickbooks, razorpay, not_applicable. Supported operators : is, is_not, in, not_in Example → gateway[is] = "stripe" |
status |
Object | No |
optional, enumerated string filter The status of this transaction. Possible values are : in_progress, success, voided, failure, timeout, needs_attention. Supported operators : is, is_not, in, not_in Example → status[is] = "success" |
payment_method |
Object | No |
optional, enumerated string filter The payment method of this transaction. Possible values are : card, cash, check, chargeback, bank_transfer, amazon_payments, paypal_express_checkout, direct_debit, alipay, unionpay, apple_pay, wechat_pay, ach_credit, sepa_credit, ideal, google_pay, sofort, bancontact, giropay, dotpay, other, upi, netbanking_emandates. Supported operators : is, is_not, in, not_in Example → payment_method[is_not] = "card" |
date |
Object | No |
optional, timestamp(UTC) in seconds filter Indicates when this transaction occurred. Supported operators : after, before, on, between Example → date[before] = "1435054328" |
include_deleted |
Boolean | No |
If set to true, includes the deleted resources in the response. For the deleted resources in the response, the '\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*deleted\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\* ' attribute will be '\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*true\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\*\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\* '. Default value: false |
updated_at |
Object | No |
optional, timestamp(UTC) in seconds filter To filter based on Example → updated_at[after] = "1243545465" |
id |
Object | No |
optional, string filter Uniquely identifies the transaction. Supported operators : is, is_not, starts_with, in, not_in Example → id[is] = "txn_88ybdbsnvf2" |
customer_id |
Object | No |
optional, string filter Identifier of the customer for which this transaction is made. Supported operators : is, is_not, starts_with, is_present, in, not_in Example → customer_id[is] = "5hjdk8nOpd" |
id_at_gateway |
Object | No |
optional, string filter The id with which this transaction is referred in gateway. Supported operators : is, is_not, starts_with Example → id_at_gateway[is_not] = "txn_5678HJS89900" |
limit |
Integer | No |
The number of resources to be returned. Default value: 10 |
gateway_account_id |
Object | No |
optional, string filter The gateway account used for this transaction. Supported operators : is, is_not, starts_with, in, not_in Example → gateway_account_id[is] = "gw_3Nl9BNeQ7438Ks1" |
amount |
Object | No |
optional, in cents filter Amount for this transaction. Supported operators : is, is_not, lt, lte, gt, gte, between Example → amount[gt] = "1200" |
type |
Object | No |
optional, enumerated string filter Type of the transaction. Possible values are : authorization, payment, refund, payment_reversal. Supported operators : is, is_not, in, not_in Example → type[is_not] = "payment" |
payment_source_id |
Object | No |
optional, string filter To filter based on Transaction payment source id. Supported operators : is, is_not, starts_with, is_present, in, not_in Example → payment_source_id[is] = "pm_3Nl8XXUQUXDVFa2" |
amount_capturable |
Object | No |
optional, in cents filter To filter based on transaction's unused authorized/blocked amount. Supported operators : is, is_not, lt, lte, gt, gte, between Example → amount_capturable[lt] = "1200" |
sort_by |
Object | No |
optional, string filter Sorts based on the specified attribute. Supported attributes : date, updated_at Supported sort-orders : asc, desc Example → sort_by[asc] = "date" This will sort the result based on the 'date' attribute in ascending(earliest first) order. |
offset |
String | No |
Determines your position in the list for pagination. To ensure that the next page is retrieved correctly, always set |
subscription_id |
Object | No |
optional, string filter Identifier of the subscription for which this transaction is made. Supported operators : is, is_not, starts_with, is_present, in, not_in Example → subscription_id[is] = "5hjdk8nOpd" |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.