GET /v1/describe/{object}
Provides a reference listing of each object that is available in your Zuora tenant.
The information returned by this call is useful if you are using CRUD: Create Export or the AQuA API to create a data source export. See Export ZOQL for more information.
Response
The response contains an XML document that lists the fields of the specified object. Each of the object's fields is represented by a <field>
element in the XML document.
Each <field>
element contains the following elements:
Element | Description |
---|---|
<name> | API name of the field. |
<label> | Name of the field in the Zuora user interface. |
<type> | Data type of the field. The possible data types are: boolean , date , datetime , decimal , integer , picklist , text , timestamp , and ZOQL . If the data type is picklist , the <field> element contains an <options> element that lists the possible values of the field. |
<contexts> | Specifies the availability of the field. If the <contexts> element lists the export context, the field is available for use in data source exports. |
The <field>
element contains other elements that provide legacy information about the field. This information is not directly related to the REST API.
Response sample:
<?xml version="1.0" encoding="UTF-8"?>
<object>
<name>ProductRatePlanCharge</name>
<label>Product Rate Plan Charge</label>
<fields>
...
<field>
<name>TaxMode</name>
<label>Tax Mode</label>
<type>picklist</type>
<options>
<option>TaxExclusive</option>
<option>TaxInclusive</option>
</options>
<contexts>
<context>export</context>
</contexts>
...
</field>
...
</fields>
</object>
It is strongly recommended that your integration checks <contexts>
elements in the response. If your integration does not check <contexts>
elements, your integration may process fields that are not available for use in data source exports. See Changes to the Describe API for more information.
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
Path parameters
Name | Type | Required | Description |
---|---|---|---|
object |
String | Yes |
API name of an object in your Zuora tenant. For example, Depending on the features enabled in your Zuora tenant, you may not be able to list the fields of some objects. |
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 |
---|---|---|---|
showCurrencyConversionInformation |
String | No |
Set the value to
|
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.