Retrieve a commitment
Authentication
Use Bearer {{token}} in the Authorization header for authentication.
Path parameters
The unique identifier (ID or number) of the commitment.
Headers
Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.
If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.
Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.
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 should not set this header.
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. This header is important in Multi-Org (MO) setups because it defines the organization context under which the API should operate—mainly used for read access or data visibility filtering. If the header is not set, the operation is performed in scope of the user’s accessible orgs.
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 (:), semicolon (;), double quote ("), and quote (').
The minor API version.
For a list of available minor versions, see API upgrades.
Response
The prepayment type of the commitment.
Note: FullyPrepaid commitments will not be considered for true-up during invoice generation.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
The flag to exclude commitment related invoice items, invoice item adjustments, credit memo items, and debit memo items from revenue accounting.
Note: This field is only available if you have the Order to Revenue feature enabled.
The specific date for period alignment, required if periodAlignmentOption is SpecificDate.
This field is used to identify if the commitment is allocation eligible in revenue recognition.
Note: This field is only available if you have the Order to Revenue feature enabled.
This field is used to dictate how to perform the accounting during revenue recognition.
Note: This field is only available if you have the Order to Revenue feature enabled.
The accounting code on the commitment for customers.
Note: This field is only available if you have the Order to Revenue feature enabled.
Determines whether the true-up invoice of a commitment is taxable. If the value is true, the tax code and tax mode are required.