GET /v1/files/{file-id}
Retrieve files such as export results, invoices, and accounting period reports.
The response content type depends on the type of file that you retrieve.
For example, if you retrieve an invoice PDF, the value of the Content-Type
header in the response is application/pdf;charset=UTF-8
.
Other content types include:
text/csv
for CSV filesapplication/msword
for Microsoft Word filesapplication/vnd.ms-excel
andapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet
for Microsoft Excel files (.xls and .xlsx respectively)application/zip
andapplication/x-gzip
for ZIP and Gzip files respectivelytext/html
for HTML filestext/plain
for text files
The response always contains character encoding information in the Content-Type
header.
For example, Content-Type: application/zip;charset=UTF-8
.
Note: The maximum file size is 2,047 MB. If you have a data request that exceeds this limit, Zuora returns the following 403 response: <security:max-object-size>2047MB</security:max-object-size>
. Submit a request at Zuora Global Support to determine if large file optimization is an option for you.
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 |
---|---|---|---|
file-id |
String | Yes |
The Zuora ID of the file to retrieve. |
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 |
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.