GET /v1/creditmemos
Note: This operation is only available if you have Invoice Settlement enabled. The Invoice Settlement feature is generally available as of Zuora Billing Release 296 (March 2021). This feature includes Unapplied Payments, Credit and Debit Memo, and Invoice Item Settlement. If you want to enable Invoice Settlement, see Invoice Settlement Enablement and Checklist Guide for more information.
Retrieves the information about all credit memos.
For a use case of this operation, see Get credit memo.
Filtering
You can use query parameters to restrict the data returned in the response. Each query parameter corresponds to one field in the response body.
If the value of a filterable field is string, you can set the corresponding query parameter to null
when filtering. Then, you can get the response data with this field value being null
.
Examples:
-
/v1/creditmemos?status=Posted
-
/v1/creditmemos?referredInvoiceId=null&status=Draft
-
/v1/creditmemos?status=Posted&type=External&sort=+number
Servers
- https://rest.test.zuora.com
- https://rest.sandbox.na.zuora.com
- https://rest.apisandbox.zuora.com
- https://rest.na.zuora.com
- https://rest.zuora.com
- https://rest.test.eu.zuora.com
- https://rest.sandbox.eu.zuora.com
- https://rest.eu.zuora.com
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Encoding |
String | No |
Include the |
Zuora-Track-Id |
String | No |
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora 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 ( |
Authorization |
String | No |
The value is in the |
Zuora-Entity-Ids |
String | No |
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header. |
Zuora-Org-Ids |
String | No |
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. |
Accept-Encoding |
String | No |
Include the If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
totalTaxExemptAmount |
Number | No |
This parameter filters the response based on the |
unappliedAmount |
Number | No |
This parameter filters the response based on the |
updatedById |
String | No |
This parameter filters the response based on the |
accountId |
String | No |
This parameter filters the response based on the |
number |
String | No |
This parameter filters the response based on the |
sort |
String | No |
This parameter restricts the order of the data returned in the response. You can use this parameter to supply a dimension you want to sort on. A sortable field uses the following form: operator field_name You can use at most two sortable fields in one URL path. Use a comma to separate sortable fields. For example: operator field_name, operator field_name operator is used to mark the order of sequencing. The operator is optional. If you only specify the sortable field without any operator, the response data is sorted in descending order by this field.
By default, the response data is displayed in descending order by credit memo number. field_name indicates the name of a sortable field. The supported sortable fields of this operation are as below:
Examples:
|
taxAmount |
Number | No |
This parameter filters the response based on the |
excludeFromAutoApplyRules |
Boolean | No |
This parameter filters the response based on the |
refundAmount |
Number | No |
This parameter filters the response based on the |
status |
String | No |
This parameter filters the response based on the Possible values:
|
createdById |
String | No |
This parameter filters the response based on the |
currency |
String | No |
This parameter filters the response based on the |
referredInvoiceId |
String | No |
This parameter filters the response based on the |
targetDate |
String | No |
This parameter filters the response based on the |
createdDate |
String | No |
This parameter filters the response based on the |
creditMemoDate |
String | No |
This parameter filters the response based on the |
page |
Integer | No |
The index number of the page that you want to retrieve. This parameter is dependent on Default value: 1 |
accountNumber |
String | No |
This parameter filters the response based on the |
appliedAmount |
Number | No |
This parameter filters the response based on the |
amount |
Number | No |
This parameter filters the response based on the |
autoApplyUponPosting |
Boolean | No |
This parameter filters the response based on the |
transferredToAccounting |
String | No |
This parameter filters the response based on the Possible values:
|
pageSize |
Integer | No |
The number of records returned per page in the response. Default value: 20 |
updatedDate |
String | No |
This parameter filters the response based on the |
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.