Products describe the specific goods or services you offer to your customers and help you track inventory or provisioning. They should be used in conjunction with Plans and Prices to configure pricing.
Quickstart API Reference
//
Retrieve a subscription
Quickstart API Reference (2025-11-12)
Zuora's Quickstart API represents a simplified programmatic experience with coverage for common eCommerce use cases only. Quickstart is NOT a replacement of the v1 API.
If you are starting new development, we recommend you use the v1 API for all your use cases. New features are only available in the v1 API. We no longer recommend Quickstart for new eCommerce development. We are not deprecating the Quickstart API and will continue to fix bugs, but we will not accept enhancement requests for the Quickstart API.
To use the Quickstart API, you must have the following features enabled on your tenant:
To find the latest changes made to the Zuora Quickstart API, check the Quickstart API Changelog.
Download OpenAPI description
Languages
Servers
Mock server
https://developer.zuora.com/_mock/other-api/quickstart-api
US Developer & Central Sandbox (incl. Test Drive)
https://rest.test.zuora.com/v2
US API Sandbox Cloud 1
https://rest.sandbox.na.zuora.com/v2
US API Sandbox Cloud 2
https://rest.apisandbox.zuora.com/v2
US Production Cloud 1
https://rest.na.zuora.com/v2
US Production Cloud 2
https://rest.zuora.com/v2
EU Developer & Central Sandbox
https://rest.test.eu.zuora.com/v2
EU API Sandbox
https://rest.sandbox.eu.zuora.com/v2
EU Production
https://rest.eu.zuora.com/v2
APAC Developer & Central Sandbox
https://rest.test.ap.zuora.com/v2
APAC Production
https://rest.ap.zuora.com/v2
Plans are collections of Prices which define the unit cost, currency, and (optional) billing cycle for both recurring and one-time purchases of Products. While Products help you track inventory or provisioning, plans and prices help you track payment terms. Different physical goods or levels of service should be represented by products, and pricing and billing cycle options should be represented by prices grouped together in a plan. This approach lets you change prices without having to change your provisioning scheme. For example, you might have a single ''Gold'' product that has prices for $100/month, $1000/year, and $50 once with the alternative billing cycle and pricing options each represented by a different plan and the recurring and one-time prices represented by different prices.
Operations
Prices define the unit cost, currency, and (optional) billing cycle for both recurring and one-time purchases of products. Products help you track inventory or provisioning, and plans and prices help you track payment terms. Different physical goods or levels of service should be represented by products, and pricing options should be represented by prices. This approach lets you change prices without having to change your provisioning scheme. For example, you might have a single ''Gold'' product that has prices for $100/month, $1000/year, and $50 once.
Operations
Order line items are non subscription based items created by an order, representing transactional charges such as one-time fees, physical goods, or professional service charges that are not sold as subscription services.
With the Order Line Items feature enabled, you have the ability to launch non-subscription and unified monetization business models in Zuora, in addition to subscription business models.
Operations
Query
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `name`, `plan_id`, `subscription_id`, `product_id`, `subscription_plan_number` Example: subscription_plans.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `charge_model`, `charge_type`, `tiers`, `subscription_item_number`, `name`, `description`, `charged_through_date`, `recurring`, `price_id`, `start_event`, `tax_code`, `tax_inclusive`, `unit_of_measure`, `quantity`, `price_base_interval`, `overage`, `subscription_plan_id`, `tiers_mode`, `processed_through_date`, `active`, `state`, `unit_amount`, `amount`, `discount_amount`, `discount_percent`, `price_change_percentage`, `price_change_option` Example: subscription_items.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: invoice_owner_account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `name`, `active`, `description`, `plan_number`, `product_id`, `active_currencies` Example: plan.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `active`, `name`, `type`, `sku`, `description` Example: product.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `tiers`, `charge_model`, `charge_type`, `name`, `description`, `revenue_recognition_rule`, `stacked_discount`, `recognized_revenue_accounting_code`, `deferred_revenue_accounting_code`, `accounting_code`, `recurring`, `start_event`, `tax_code`, `tax_inclusive`, `taxable`, `unit_of_measure`, `quantity`, `min_quantity`, `max_quantity`, `price_base_interval`, `discount_level`, `overage`, `plan_id`, `tiers_mode`, `apply_discount_to`, `prepayment`, `drawdown`, `discount_amounts`, `unit_amounts`, `discount_percent`, `amounts`, `price_change_percentage`, `price_change_option`, `price_increase_option` Example: price.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `account_id`, `address`, `home_phone`, `first_name`, `last_name`, `email`, `work_email`, `nickname`, `other_phone`, `work_phone`, `mobile_phone`, `tax_region`, `other_phone_type`, `fax` Example: bill_to.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance` Example: prepaid_balance.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`validity_periods` Example: prepaid_balances.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance`, `overage_rated_amount`, `overage_rated_quantity` Example: validity_period.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`transaction_date`, `type`, `quantity` Example: transactions.fields[]=id,created_time
Allows you to expand responses by including related object information in a single call. See the Expand responses section of the Quickstart API Tutorials for detailed instructions.
A case-sensitive filter on the list. See the Filter lists section of the Quickstart API Tutorial for detailed instructions.
Note that the filters on this operation are only applicable to the related objects. For example, when you are calling the "Retrieve a billing document" operation, you can use the filter[] parameter on the related objects such as filter[]=items[account_id].EQ:8ad09e208858b5cf0188595208151c63
The maximum number of results to return in a single page. If the specified page_size is less than 1 or greater than 99, Zuora will return a 400 error.
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: subscription.fields[]=id,created_time
Headers
A custom identifier for tracking API requests. If you set a value for this header, Zuora returns the same value in the response header. This header enables you to track your API calls to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), or quote (').
Making asynchronous requests allows you to scale your applications more efficiently by leveraging Zuora's infrastructure to enqueue and execute requests for you without blocking. These requests also use built-in retry semantics, which makes them much less likely to fail for non-deterministic reasons, even in extreme high-throughput scenarios. Meanwhile, when you send a request to one of these endpoints, you can expect to receive a response in less than 150 milliseconds and these calls are unlikely to trigger rate limit errors. If set to true, Zuora returns a 202 Accepted response, and the response body contains only a request ID.
Default false
An entity ID. If you have Multi-entity enabled and the authorization token is valid for more than one entity, you must use this header to specify which entity to perform the operation on. If the authorization token is only valid for a single entity or you do not have Multi-entity enabled, you do not need to set this header.
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. This idempotency key should be a unique value, and the Zuora server identifies subsequent retries of the same request using this value. For more information, see Idempotent Requests.
Include a accept-encoding: gzip header to compress responses, which can reduce the bandwidth required for a response. If specified, Zuora automatically compresses responses that contain over 1000 bytes. For more information about this header, see Request and Response Compression.
Include a content-encoding: gzip header to compress a request. Upload a gzipped file for the payload if you specify this header. For more information, see Request and Response Compression.
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.
The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails.
If the header is not set, the operation is performed in scope of the user's accessible orgs.
- Mock serverhttps://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions/{subscription_id}
- US Developer & Central Sandbox (incl. Test Drive)https://rest.test.zuora.com/v2/subscriptions/{subscription_id}
- US API Sandbox Cloud 1https://rest.sandbox.na.zuora.com/v2/subscriptions/{subscription_id}
- US API Sandbox Cloud 2https://rest.apisandbox.zuora.com/v2/subscriptions/{subscription_id}
- US Production Cloud 1https://rest.na.zuora.com/v2/subscriptions/{subscription_id}
- US Production Cloud 2https://rest.zuora.com/v2/subscriptions/{subscription_id}
- EU Developer & Central Sandboxhttps://rest.test.eu.zuora.com/v2/subscriptions/{subscription_id}
- EU API Sandboxhttps://rest.sandbox.eu.zuora.com/v2/subscriptions/{subscription_id}
- EU Productionhttps://rest.eu.zuora.com/v2/subscriptions/{subscription_id}
- APAC Developer & Central Sandboxhttps://rest.test.ap.zuora.com/v2/subscriptions/{subscription_id}
- APAC Productionhttps://rest.ap.zuora.com/v2/subscriptions/{subscription_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions/{subscription_id}?fields%5B%5D=id%2Ccreated_time&subscription_plans.fields%5B%5D=id%2Ccreated_time&subscription_items.fields%5B%5D=id%2Ccreated_time&account.fields%5B%5D=id%2Ccreated_time&invoice_owner_account.fields%5B%5D=id%2Ccreated_time&plan.fields%5B%5D=id%2Ccreated_time&product.fields%5B%5D=id%2Ccreated_time&price.fields%5B%5D=id%2Ccreated_time&bill_to.fields%5B%5D=id%2Ccreated_time&prepaid_balance.fields%5B%5D=id%2Ccreated_time&prepaid_balances.fields%5B%5D=id%2Ccreated_time&validity_period.fields%5B%5D=id%2Ccreated_time&transactions.fields%5B%5D=id%2Ccreated_time&expand%5B%5D=string&filter%5B%5D=string&page_size=1&subscription.fields%5B%5D=id%2Ccreated_time' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'accept-encoding: string' \
-H 'async: false' \
-H 'content-encoding: string' \
-H 'idempotency-key: string' \
-H 'zuora-entity-ids: string' \
-H 'zuora-org-ids: string' \
-H 'zuora-track-id: string'Default Response
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
The date and time when the object was last updated in ISO 8601 UTC format.
The date and time when the object was created in ISO 8601 UTC format.
Set of user-defined fields associated with this object. Useful for storing additional information about the object in a structured format.
Status of the subscription.
Enum"draft""pending_activation""pending_acceptance""active""expired""canceled""paused"
The version of the subscription. This version can be used in the filter[] query parameter to filter subscriptions.
Identifier of the account that owns the invoice associated with this subscription.
If this field is set to true, the subscription automatically renews at the end of the current term.
Date when the subscribed-to service is activated.
Example: "2023-01-01"
Date when all the services or products in the subscription are accepted by the subscriber.
Example: "2023-01-01"
If true, the subscription is billed separately from other subscriptions. If false, the subscription is included with other subscriptions in the account invoice. The default is false.
Total prepaid units available during a subscription. It is an aggregate of all funds under a subscription.
3-letter ISO 4217 currency code. This field is available only if you have the Multiple Currencies feature enabled.
The last booking date of the subscription object. You can override the date value when creating a subscription through the "Subscribe and Amend" API. The default value today is set per the user's timezone. The value of this field is as follows:
- For a new subscription created by the Subscribe and Amend APIs, this field has the value of the subscription creation date.
- For a subscription changed by an amendment, this field has the value of the amendment booking date.
- For a subscription created or changed by an order, this field has the value of the order date.
Example: "2023-01-01"
The billing document settings for the customer.
Response
application/json
{ "id": "8ad08ccf8437067601843a7af4e64rq3", "custom_fields": { "field__c": "custom field value" }, "subscription_number": "A-S0001332401234", "state": "active", "account_id": "2c92c0f86a8dd422016a9e7a70116b0d", "invoice_owner_account_id": "2c92c0f86a8dd422016a9e7a70116b0d", "auto_renew": true, "latest_version": true, "initial_term": { "interval_count": 1, "interval": "month", "type": "termed" }, "current_term": { "interval_count": 1, "interval": "month", "start_date": "2022-07-01", "type": "termed", "end_date": "2022-08-01" }, "start_date": "2022-07-01", "end_date": "2022-08-01", "description": "Create Subscription", "contract_effective": "2022-07-01", "service_activation": "2022-07-01", "customer_acceptance": "2022-07-01", "invoice_separately": false, "order_number": "O-00020812" }
Request
Updates the specified subscription by setting the values of the parameters passed. Any parameters not provided will be left unchanged.
Security
bearerAuth
Query
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `name`, `plan_id`, `subscription_id`, `product_id`, `subscription_plan_number` Example: subscription_plans.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `charge_model`, `charge_type`, `tiers`, `subscription_item_number`, `name`, `description`, `charged_through_date`, `recurring`, `price_id`, `start_event`, `tax_code`, `tax_inclusive`, `unit_of_measure`, `quantity`, `price_base_interval`, `overage`, `subscription_plan_id`, `tiers_mode`, `processed_through_date`, `active`, `state`, `unit_amount`, `amount`, `discount_amount`, `discount_percent`, `price_change_percentage`, `price_change_option` Example: subscription_items.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: invoice_owner_account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `name`, `active`, `description`, `plan_number`, `product_id`, `active_currencies` Example: plan.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `active`, `name`, `type`, `sku`, `description` Example: product.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `tiers`, `charge_model`, `charge_type`, `name`, `description`, `revenue_recognition_rule`, `stacked_discount`, `recognized_revenue_accounting_code`, `deferred_revenue_accounting_code`, `accounting_code`, `recurring`, `start_event`, `tax_code`, `tax_inclusive`, `taxable`, `unit_of_measure`, `quantity`, `min_quantity`, `max_quantity`, `price_base_interval`, `discount_level`, `overage`, `plan_id`, `tiers_mode`, `apply_discount_to`, `prepayment`, `drawdown`, `discount_amounts`, `unit_amounts`, `discount_percent`, `amounts`, `price_change_percentage`, `price_change_option`, `price_increase_option` Example: price.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `account_id`, `address`, `home_phone`, `first_name`, `last_name`, `email`, `work_email`, `nickname`, `other_phone`, `work_phone`, `mobile_phone`, `tax_region`, `other_phone_type`, `fax` Example: bill_to.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance` Example: prepaid_balance.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`validity_periods` Example: prepaid_balances.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance`, `overage_rated_amount`, `overage_rated_quantity` Example: validity_period.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`transaction_date`, `type`, `quantity` Example: transactions.fields[]=id,created_time
Allows you to expand responses by including related object information in a single call. See the Expand responses section of the Quickstart API Tutorials for detailed instructions.
A case-sensitive filter on the list. See the Filter lists section of the Quickstart API Tutorial for detailed instructions.
Note that the filters on this operation are only applicable to the related objects. For example, when you are calling the "Retrieve a billing document" operation, you can use the filter[] parameter on the related objects such as filter[]=items[account_id].EQ:8ad09e208858b5cf0188595208151c63
The maximum number of results to return in a single page. If the specified page_size is less than 1 or greater than 99, Zuora will return a 400 error.
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: subscription.fields[]=id,created_time
Headers
Bodyapplication/jsonrequiredA custom identifier for tracking API requests. If you set a value for this header, Zuora returns the same value in the response header. This header enables you to track your API calls to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), or quote (').
Making asynchronous requests allows you to scale your applications more efficiently by leveraging Zuora's infrastructure to enqueue and execute requests for you without blocking. These requests also use built-in retry semantics, which makes them much less likely to fail for non-deterministic reasons, even in extreme high-throughput scenarios. Meanwhile, when you send a request to one of these endpoints, you can expect to receive a response in less than 150 milliseconds and these calls are unlikely to trigger rate limit errors. If set to true, Zuora returns a 202 Accepted response, and the response body contains only a request ID.
Default false
An entity ID. If you have Multi-entity enabled and the authorization token is valid for more than one entity, you must use this header to specify which entity to perform the operation on. If the authorization token is only valid for a single entity or you do not have Multi-entity enabled, you do not need to set this header.
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. This idempotency key should be a unique value, and the Zuora server identifies subsequent retries of the same request using this value. For more information, see Idempotent Requests.
Include a accept-encoding: gzip header to compress responses, which can reduce the bandwidth required for a response. If specified, Zuora automatically compresses responses that contain over 1000 bytes. For more information about this header, see Request and Response Compression.
Include a content-encoding: gzip header to compress a request. Upload a gzipped file for the payload if you specify this header. For more information, see Request and Response Compression.
Set of user-defined fields associated with this object. Useful for storing additional information about the object in a structured format.
Container for the contract effective, service activation, and customer acceptance dates of the order action or subscription.
- If Zuora is configured to require service activation and the
service_activationfield is not set for asubscription_plansorder action or the "Create a subscription" operation, apendingorder and/or apending_activationsubscription are created. - If Zuora is configured to require customer acceptance and the
customer_acceptancefield is not set for asubscription_plansorder action or the "Create a subscription" operation, apendingorder and/or apending_acceptancesubscription are created. At the same time, if the service activation date field is also required and not set, apendingorder and/or apending_activationsubscription are created instead. - If Zuora is configured to require service activation and the
service_activationfield is not set for any of the following order actions or the "Update a subscription" operation, apendingorder is created. The subscription status is not impacted. Note: This feature is in Limited Availability. If you want to have access to the feature, submit a request at Zuora Global Support.add_subscription_plansupdate_subscription_plansremove_subscription_plansrenewterms
customer_acceptance field is not set for any of the following order actions or the "Update a subscription" operation, a pending order is created. The subscription status is not impacted. Note: This feature is in Limited Availability. If you want to have access to the feature, submit a request at Zuora Global Support. add_subscription_plansupdate_subscription_plansremove_subscription_plansrenewterms
Identifier of the account that owns the invoice associated with this subscription.
Identifier of the account that owns the invoice associated with this subscription.
Identifier of the account that owns the subscription. Subscription owner account can be different from the invoice owner account.
Identifier of the account that owns the subscription. Subscription owner account can be different from the invoice owner account.
Specify this field if you want to add one or multiple subscription plans to this subscription.
Specify this field if you want to remove one or multiple subscription plans from this subscription.
Specify this field if you want to replace one or multiple subscription plans to this subscription.
Note: This field is currently not supported if you have Billing - Revenue Integration enabled. When Billing - Revenue Integration is enabled, the replace subscription plan type of order action will no longer be applicable in Zuora Billing.
Specify this field when renewing a subscription.
The billing document settings for the customer.
Separates a single subscription from other subscriptions and creates an invoice for this subscription. If the value is true, the subscription is billed separately from other subscriptions. If the value is false, the subscription is included with other subscriptions in the account invoice.
- Mock serverhttps://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions/{subscription_id}
- US Developer & Central Sandbox (incl. Test Drive)https://rest.test.zuora.com/v2/subscriptions/{subscription_id}
- US API Sandbox Cloud 1https://rest.sandbox.na.zuora.com/v2/subscriptions/{subscription_id}
- US API Sandbox Cloud 2https://rest.apisandbox.zuora.com/v2/subscriptions/{subscription_id}
- US Production Cloud 1https://rest.na.zuora.com/v2/subscriptions/{subscription_id}
- US Production Cloud 2https://rest.zuora.com/v2/subscriptions/{subscription_id}
- EU Developer & Central Sandboxhttps://rest.test.eu.zuora.com/v2/subscriptions/{subscription_id}
- EU API Sandboxhttps://rest.sandbox.eu.zuora.com/v2/subscriptions/{subscription_id}
- EU Productionhttps://rest.eu.zuora.com/v2/subscriptions/{subscription_id}
- APAC Developer & Central Sandboxhttps://rest.test.ap.zuora.com/v2/subscriptions/{subscription_id}
- APAC Productionhttps://rest.ap.zuora.com/v2/subscriptions/{subscription_id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PATCH \
'https://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions/{subscription_id}?fields%5B%5D=id%2Ccreated_time&subscription_plans.fields%5B%5D=id%2Ccreated_time&subscription_items.fields%5B%5D=id%2Ccreated_time&account.fields%5B%5D=id%2Ccreated_time&invoice_owner_account.fields%5B%5D=id%2Ccreated_time&plan.fields%5B%5D=id%2Ccreated_time&product.fields%5B%5D=id%2Ccreated_time&price.fields%5B%5D=id%2Ccreated_time&bill_to.fields%5B%5D=id%2Ccreated_time&prepaid_balance.fields%5B%5D=id%2Ccreated_time&prepaid_balances.fields%5B%5D=id%2Ccreated_time&validity_period.fields%5B%5D=id%2Ccreated_time&transactions.fields%5B%5D=id%2Ccreated_time&expand%5B%5D=string&filter%5B%5D=string&page_size=1&subscription.fields%5B%5D=id%2Ccreated_time' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'accept-encoding: string' \
-H 'async: false' \
-H 'content-encoding: string' \
-H 'idempotency-key: string' \
-H 'zuora-entity-ids: string' \
-H 'zuora-track-id: string' \
-d '{
"description": "new subscription description",
"add_subscription_plans": [
{
"subscription_plan": {
"plan_id": "8ad0824e7c980196017c9f3a60763eca",
"prices": [
{
"price_id": "8ad084a67c9801a7017c9f3a6ba008d4",
"amount": 15
}
],
"unique_token": "SUB_PLAN_1530903",
"custom_fields": {
"field__c": "custom field value"
}
},
"start_on": {
"contract_effective": "2022-07-01",
"service_activation": "2022-07-01",
"customer_acceptance": "2022-07-01"
}
}
],
"update_subscription_plans": [
{
"subscription_plan": {
"subscription_plan_id": "8ad0823f8292a2ce0182a31fe5ec220d",
"subscription_items": [
{
"id": "8ad0823f8292a2ce0182a31fe5ec2210",
"quantity": 30,
"unit_amount": 239.99,
"start_date": "2022-08-15"
},
{
"id": "8ad0823f8292a2ce0182a31fe5ec2213",
"discount_percent": 20
}
]
},
"start_on": {
"contract_effective": "2022-08-01",
"service_activation": "2022-08-15",
"customer_acceptance": "2022-08-30"
}
}
],
"remove_subscription_plans": [
{
"subscription_plan_id": "8ad0823f8292a2ce0182a31fe5ec2213",
"start_on": {
"contract_effective": "2022-06-01",
"service_activation": "2022-06-01",
"customer_acceptance": "2022-06-01"
}
}
],
"custom_fields": {
"field__c": "custom field value"
}
}'Default Response
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
The date and time when the object was last updated in ISO 8601 UTC format.
The date and time when the object was created in ISO 8601 UTC format.
Set of user-defined fields associated with this object. Useful for storing additional information about the object in a structured format.
Status of the subscription.
Enum"draft""pending_activation""pending_acceptance""active""expired""canceled""paused"
The version of the subscription. This version can be used in the filter[] query parameter to filter subscriptions.
Identifier of the account that owns the invoice associated with this subscription.
If this field is set to true, the subscription automatically renews at the end of the current term.
Date when the subscribed-to service is activated.
Example: "2023-01-01"
Date when all the services or products in the subscription are accepted by the subscriber.
Example: "2023-01-01"
If true, the subscription is billed separately from other subscriptions. If false, the subscription is included with other subscriptions in the account invoice. The default is false.
Total prepaid units available during a subscription. It is an aggregate of all funds under a subscription.
3-letter ISO 4217 currency code. This field is available only if you have the Multiple Currencies feature enabled.
The last booking date of the subscription object. You can override the date value when creating a subscription through the "Subscribe and Amend" API. The default value today is set per the user's timezone. The value of this field is as follows:
- For a new subscription created by the Subscribe and Amend APIs, this field has the value of the subscription creation date.
- For a subscription changed by an amendment, this field has the value of the amendment booking date.
- For a subscription created or changed by an order, this field has the value of the order date.
Example: "2023-01-01"
The billing document settings for the customer.
Response
application/json
{ "id": "8ad09c4b819040ce018191b8433c4b5a", "custom_fields": { "field__c": "custom field value" }, "subscription_number": "A-S00013199", "state": "active", "account_id": "2c92c0f86a8dd422016a9e7a70116b0d", "auto_renew": true, "latest_version": true, "initial_term": { "interval_count": 1, "interval": "month", "type": "evergreen" }, "current_term": { "interval_count": 0, "start_date": "2022-07-01", "type": "evergreen" }, "start_date": "2022-06-01", "description": "Update Custom Fields", "contract_effective": "2022-06-01", "service_activation": "2022-06-01", "customer_acceptance": "2022-06-01", "invoice_separately": false, "invoice_owner_account_id": "2c92c0f86ab120d4016ab3799e955147", "order_number": "O-00020539" }
Request
Returns a dictionary with a data property that contains an array of subscriptions, starting after the cursor, if used. Each entry in the array is a separate subscription object. If no more subscriptions are available, the resulting array will be empty. This request should never return an error.
Security
bearerAuth
Query
A cursor for use in pagination. A cursor defines the starting place in a list. For instance, if you make a list request and receive 100 objects, ending with next_page=W3sib3JkZXJ=, your subsequent call can include cursor=W3sib3JkZXJ= in order to fetch the next page of the list.
Allows you to expand responses by including related object information in a single call. See the Expand responses section of the Quickstart API Tutorials for detailed instructions.
A case-sensitive filter on the list. See the Filter lists section of the Quickstart API Tutorials for detailed instructions.
A case-sensitive query parameter that specifies the sort order of the list, which can be either ascending (e.g. account_number.asc) or descending (e.g. account_number.desc). You cannot sort on properties that are arrays. If the array-type properties are specified for the sort[] parameter, they are ignored.
The maximum number of results to return in a single page. If the specified page_size is less than 1 or greater than 99, Zuora will return a 400 error.
Default 30
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `name`, `plan_id`, `subscription_id`, `product_id`, `subscription_plan_number` Example: subscription_plans.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `charge_model`, `charge_type`, `tiers`, `subscription_item_number`, `name`, `description`, `charged_through_date`, `recurring`, `price_id`, `start_event`, `tax_code`, `tax_inclusive`, `unit_of_measure`, `quantity`, `price_base_interval`, `overage`, `subscription_plan_id`, `tiers_mode`, `processed_through_date`, `active`, `state`, `unit_amount`, `amount`, `discount_amount`, `discount_percent`, `price_change_percentage`, `price_change_option` Example: subscription_items.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `auto_pay`, `account_number`, `bill_to_id`, `sold_to_id`, `billing_document_settings`, `communication_profile_id`, `crm_id`, `sales_rep`, `parent_account_id`, `payment_gateway`, `payment_terms`, `remaining_credit_memo_balance`, `remaining_debit_memo_balance`, `remaining_invoice_balance`, `remaining_payment_balance`, `sequence_set_id`, `tax_certificate`, `batch`, `tax_identifier`, `bill_cycle_day`, `description`, `name`, `currency`, `default_payment_method_id`, `enabled` Example: invoice_owner_account.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `name`, `active`, `description`, `plan_number`, `product_id`, `active_currencies` Example: plan.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `start_date`, `end_date`, `active`, `name`, `type`, `sku`, `description` Example: product.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `tiers`, `charge_model`, `charge_type`, `name`, `description`, `revenue_recognition_rule`, `stacked_discount`, `recognized_revenue_accounting_code`, `deferred_revenue_accounting_code`, `accounting_code`, `recurring`, `start_event`, `tax_code`, `tax_inclusive`, `taxable`, `unit_of_measure`, `quantity`, `min_quantity`, `max_quantity`, `price_base_interval`, `discount_level`, `overage`, `plan_id`, `tiers_mode`, `apply_discount_to`, `prepayment`, `drawdown`, `discount_amounts`, `unit_amounts`, `discount_percent`, `amounts`, `price_change_percentage`, `price_change_option`, `price_increase_option` Example: price.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `account_id`, `address`, `home_phone`, `first_name`, `last_name`, `email`, `work_email`, `nickname`, `other_phone`, `work_phone`, `mobile_phone`, `tax_region`, `other_phone_type`, `fax` Example: bill_to.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance` Example: prepaid_balance.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`validity_periods` Example: prepaid_balances.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`prepaid_UOM`, `start_date`, `end_date`, `total_balance`, `remaining_balance`, `overage_rated_amount`, `overage_rated_quantity` Example: validity_period.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`transaction_date`, `type`, `quantity` Example: transactions.fields[]=id,created_time
Allows you to specify which fields are returned in the response.
Accepted values
`custom_fields`, `created_by_id`, `updated_by_id`, `created_time`, `id`, `updated_time`, `subscription_number`, `state`, `account_id`, `invoice_owner_account_id`, `auto_renew`, `version`, `initial_term`, `current_term`, `renewal_term`, `start_date`, `end_date`, `description`, `contract_effective`, `service_activation`, `customer_acceptance`, `invoice_separately`, `latest_version`, `payment_terms`, `billing_document_settings`, `bill_to_id`, `sold_to_id`, `contracted_mrr`, `currency`, `cancel_reason`, `last_booking_date`, `order_number` Example: subscription.fields[]=id,created_time
Headers
A custom identifier for tracking API requests. If you set a value for this header, Zuora returns the same value in the response header. This header enables you to track your API calls to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), or quote (').
Making asynchronous requests allows you to scale your applications more efficiently by leveraging Zuora's infrastructure to enqueue and execute requests for you without blocking. These requests also use built-in retry semantics, which makes them much less likely to fail for non-deterministic reasons, even in extreme high-throughput scenarios. Meanwhile, when you send a request to one of these endpoints, you can expect to receive a response in less than 150 milliseconds and these calls are unlikely to trigger rate limit errors. If set to true, Zuora returns a 202 Accepted response, and the response body contains only a request ID.
Default false
An entity ID. If you have Multi-entity enabled and the authorization token is valid for more than one entity, you must use this header to specify which entity to perform the operation on. If the authorization token is only valid for a single entity or you do not have Multi-entity enabled, you do not need to set this header.
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. This idempotency key should be a unique value, and the Zuora server identifies subsequent retries of the same request using this value. For more information, see Idempotent Requests.
Include a accept-encoding: gzip header to compress responses, which can reduce the bandwidth required for a response. If specified, Zuora automatically compresses responses that contain over 1000 bytes. For more information about this header, see Request and Response Compression.
Include a content-encoding: gzip header to compress a request. Upload a gzipped file for the payload if you specify this header. For more information, see Request and Response Compression.
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.
The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails.
If the header is not set, the operation is performed in scope of the user's accessible orgs.
- Mock serverhttps://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions
- US Developer & Central Sandbox (incl. Test Drive)https://rest.test.zuora.com/v2/subscriptions
- US API Sandbox Cloud 1https://rest.sandbox.na.zuora.com/v2/subscriptions
- US API Sandbox Cloud 2https://rest.apisandbox.zuora.com/v2/subscriptions
- US Production Cloud 1https://rest.na.zuora.com/v2/subscriptions
- US Production Cloud 2https://rest.zuora.com/v2/subscriptions
- EU Developer & Central Sandboxhttps://rest.test.eu.zuora.com/v2/subscriptions
- EU API Sandboxhttps://rest.sandbox.eu.zuora.com/v2/subscriptions
- EU Productionhttps://rest.eu.zuora.com/v2/subscriptions
- APAC Developer & Central Sandboxhttps://rest.test.ap.zuora.com/v2/subscriptions
- APAC Productionhttps://rest.ap.zuora.com/v2/subscriptions
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.zuora.com/_mock/other-api/quickstart-api/subscriptions?cursor=string&expand%5B%5D=string&filter%5B%5D=string&sort%5B%5D=string&page_size=30&fields%5B%5D=id%2Ccreated_time&subscription_plans.fields%5B%5D=id%2Ccreated_time&subscription_items.fields%5B%5D=id%2Ccreated_time&account.fields%5B%5D=id%2Ccreated_time&invoice_owner_account.fields%5B%5D=id%2Ccreated_time&plan.fields%5B%5D=id%2Ccreated_time&product.fields%5B%5D=id%2Ccreated_time&price.fields%5B%5D=id%2Ccreated_time&bill_to.fields%5B%5D=id%2Ccreated_time&prepaid_balance.fields%5B%5D=id%2Ccreated_time&prepaid_balances.fields%5B%5D=id%2Ccreated_time&validity_period.fields%5B%5D=id%2Ccreated_time&transactions.fields%5B%5D=id%2Ccreated_time&subscription.fields%5B%5D=id%2Ccreated_time' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'accept-encoding: string' \
-H 'async: false' \
-H 'content-encoding: string' \
-H 'idempotency-key: string' \
-H 'zuora-entity-ids: string' \
-H 'zuora-org-ids: string' \
-H 'zuora-track-id: string'Default Response
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
Response
application/json
{ "next_page": "W3sib3JkZXJCeSI6eyJmaWVsZCI6IlVwZGF0ZWREYXRlIiwib3JkZXIiOiJERVNDIn0sInZhbHVlIjoiMjAyMi0xMi0yMFQxMjoyODo1NC0wODowMCJ9LHsib3JkZXJCeSI6eyJmaWVsZCI6IklkIiwib3JkZXIiOiJERVNDIn0sInZhbHVlIjoiMmM5MmMwZjk2YWJjMTdkZTAxNmFiZDYyYmQwYzU4NTQifV0=", "data": [ { … }, { … }, { … }, { … }, { … } ] }
A subscription plan is part of a subscription or an amendment to a subscription, and it comes from a price. Like a product and its plans, a subscription can have one or more subscription plans. Subscription plans represent a price or a collection of prices for a service you sell. An individual subscription plan contains all prices specific to a particular subscription.
Operations
Fulfillments are subordinate objects attached to their related order line item. You can manage the entire order line item lifecycle through fulfillments in the following ways:
- Create and attach fulfillments to an order line item to track the shipment or return status.
- Trigger billing based on the fulfillment state and generate billing documents based on the fulfillments accordingly.
- Create and attach fulfillment items to a fulfillment to keep track of all the assets in your system.
Operations
Credit memos reduce invoice and account balances. By applying one or more credit memos to invoices with positive balances, you can reduce the invoice balances in the same way as applying a payment to an invoice. For more information about credit memos, see Credit and debit memos.
Operations
Debit memos increase the amount a customer owes. Debit memos can be used to correct undercharging on an invoice or to levy ad hoc charges outside the context of a subscription. Just like an invoice, debit memo balances can be settled by applying either a payment or a credit memo. For more information about debit memos, see Credit and debit memos.
Operations
Bill runs automatically create invoices for your customers on a set schedule, as well as create invoices for your customers, as needed. A bill run gathers information from one or more customer accounts and generates invoices for those accounts. The operations in this section allows you to create, update, get, or delete bill runs.
Operations
The Bill Run Previews operations allow you to generates a preview of future billing document items for a batch of accounts through a bill run. A bill run preivew job also generates a downloadable CSV file containing a preview of invoice item data for the customer account batch.
Operations
The TaxationItem object is used to add a tax amount to an invoice item. Z-Tax and third-party tax engines such as Avalara or Connect tax engine can create TaxationItem objects. Before you use the Taxation Item object, you have to configure Z-Tax, Avalara, or Connect tax engine, as the object's fields rely on the values you create during the configuration process.
Operations
Payment methods represent your customer's payment instruments. They can be used to collect payments or saved to Account objects to store instrument details for future payments.
Important: The type field in the request body schema of the Create a payment method operation enumerates the supported payment methods. Not all payment gateways support all these payment method types. Check Supported payment methods to check the supported payment methods for each gateway.
If you need to create payment methods outside the scope of this operaton, you have to use the Create a payment method operation of the v1 API instead of the Quickstart API. We do not plan to add additional payment methods to the Quickstart API. Any new payment methods will only be available through the v1 API and Zuora client libraries.
Operations
Payment runs are used to collect payments using electronic payment methods. Even if a payment was made to an invoice but had an error, if an invoice has a positive balance and meets all the filter criteria for the payment run, Zuora will pick up the invoice for processing in the payment run.
Zuora supports two type of payment runs: ad hoc and recurring. These are similar to ad hoc and scheduled bill runs
Operations
The Payment Schedules feature enables you to collect a series of payments following customized timelines and rules. You have the flexibility to leverage a payment schedule to process either a single payment or multiple payments.
You can leverage this feature to split invoice or account balances into several installments, and then automatically process payments for the installments. Payment schedules can also be used to collect external payments made for the installments. Meanwhile, we’ve provided you the capability to easily manage and modify existing schedules, as well as to manually retry failed payments with updated configurations.
Operations
Note: The API operations in this section have been deprecated.
Billing Documents represent your customer's invoices, credit memos and debit memos. Invoices are statements of amounts owed by a customer, and are either generated one-off, or generated periodically from a subscription. They contain invoice items, and proration adjustments that may be caused by changes to a subscription. If your invoice is configured to be charged automatically, Zuora automatically finalizes your invoice and attempts payment otherwise Zuora will email the invoice to your customer and await payment. Any customer credit memos may be applied before determining the amount due for the invoice (i.e., the amount that will be charged).
Operations