Create a job to export audit trail data for a meter
Creates a background job to export the audit trail entries for a specific meter in Zuora Mediation. This API is for large-scale, offline access to audit data. Only one export job is processed per tenant at a time, and each export has a record limit, for example, up to 5 million rows per report. Use the returned requestId with the “Retrieve the list of export jobs for a meter” API operation to track the job status and retrieve the generated file names from fileList, then download them using the “Retrieve the presigned URL for an export job” API operation.
Authentication
Use Bearer {{token}} in the Authorization header for authentication.
Path parameters
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 (').
Query parameters
Type of the export. SAMPLE indicates an export of success records, ERROR indicates an export of error records.
Specifies the type of run. DEBUG indicates a test run, NORMAL indicates a live run.
A list of specific run IDs to export. For example, R-000001, R-000002.
Filters audit entries by their run status. If omitted, all statuses are included. Statuses are case-sensitive. Possible values:
- NEVER_RUN
- TESTING
- TESTING_FAILED
- TESTING_PASSED
- RUNNING
- PAUSED
- COMPLETED
- FAILED
- CANCELED
- INITIALIZING
- USAGE_PUSHING
- PUSH_COMPLETED
- CONSUME_COMPLETED
Required format for the exported data.
Supported values are:
csv: Row-based CSV outputparquet: Columnar Parquet outputavro: Avro output
If omitted, csv is used by default for backward compatibility.
Optional compression algorithm applied to the exported file(s).
Supported values are:
none: No compression (default)gzip: GZIP compressionlz4: LZ4 compressionzstd: Zstandard compression
If omitted, none is used and the export produces an uncompressed
file. When a compression value other than none is specified, the
generated export files are stored in compressed form and must be
decompressed by the client after download.