# Retrieve the audit trail entries for a meter

Retrieves the audit trail entries for a specific meter in Zuora Mediation. The API provides detailed, record-level information about what happened during processing, including Payload and error details, operator information, and the trace ID/event ID.

Endpoint: GET /meters/{meterId}/auditTrail/entries
Version: 2026-02-20
Security: bearerAuth

## Path parameters:

  - `meterId` (integer, required)
    ID of the meter.

## Query parameters:

  - `exportType` (string, required)
    Type of the export. SAMPLE indicates an export of success records, ERROR indicates an export of error records.
    Enum: "SAMPLE", "ERROR"

  - `runType` (string, required)
    Specifies the type of run. DEBUG indicates a test run, NORMAL indicates a live run.
    Enum: "DEBUG", "NORMAL"

  - `sessionId` (string)
    A specific session ID.
    Example: "R-000001"

  - `queryFromTime` (string, required)
    The minimum timestamp of the audit trail data. The standard used is ISO 8601 with timezones.
    Example: "2025-07-18 T00:00:00Z"

  - `queryToTime` (string, required)
    The maximum timestamp of the audit trail data. The standard used is ISO 8601 with timezones.
    Example: "2025-07-18 T00:00:00Z"

  - `operatorId` (string)
    The ID of the operator. The Operator ID is displayed for each operator node, for both current meters and historic runs. On the Mediation UI, click on a test ID or session ID to see the details of the run.

  - `pageSize` (integer)
    Page size for pagination.

  - `cursor` (string)
    nextPage token from previous response.
    Example: "W3sib3JkZXJ="

## Header parameters:

  - `Content-Type` (string, required)
    Specify the content type of the request body. Use application/json.

  - `Accept-Encoding` (string)
    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.

  - `Content-Encoding` (string)
    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.

  - `Zuora-Entity-Ids` (string)
    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.

  - `Zuora-Org-Ids` (string)
    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.

  - `Zuora-Track-Id` (string)
    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 (').

## Response 200 fields (application/json):

  - `success` (boolean)
    Indicates whether the request was successful.

  - `data` (array)
    List of audit trail entries for the specified meter. Each object represents a recorded event or operation associated with the meter.

  - `data.errorTime` (string)
    Timestamp when an error occurred during the meter operation or event processing, if applicable.

  - `data.timestamp` (string)
    Timestamp when the audit entry was created, representing the exact time the event or operation was recorded.

  - `data.errorCode` (string)
    Unique identifier for the specific error type, used to categorize and troubleshoot issues. Present only when an error has occurred.

  - `data.errorMessage` (string)
    Descriptive message explaining the cause or nature of the error. Useful for debugging or logging.

  - `data.payload` (object)
    Raw event data or metadata associated with the audited action, including event content, request body, or contextual details.

  - `data.eventId` (string)
    Unique identifier assigned to the audited event. Enables correlation of events across systems for traceability.

  - `data.traceId` (string)
    Unique identifier used to trace the end-to-end flow of an event through the system. Useful for debugging distributed processes.

  - `data.operatorType` (string)
    Type of processor used. Examples: MAP, ENRICHMENT
    Enum: "ACCUMULATOR", "AGGREGATOR", "BILLING_RATING", "CLICKHOUSE_SINK", "CLICKHOUSE_SOURCE", "DEDUPLICATE", "EVENT_STORE_SINK", "EVENT_STORE_SOURCE", "FILTER", "HTTP", "KAFKA_SINK", "KAFKA_SOURCE", "LOCAL_FS_SOURCE", "MAP", "NATS_SINK", "NATS_SOURCE", "PARTITION", "RATING", "S3_SINK", "S3_SOURCE", "SAMPLE_COMMITTABLE_SINK", "SCRIPT_ACCUMULATOR", "SCRIPT_AGGREGATOR", "SCRIPT_FILTER", "SCRIPT_MAP", "SNOWFLAKE_ERROR", "SNOWFLAKE_SINK", "SNOWFLAKE_SOURCE", "STREAMING_API_SOURCE", "SUBSCRIPTION_LOOKUP", "TSTORE_SINK", "USAGE_RECORD_SINK", "USER_INPUT_SOURCE"

  - `data.operatorName` (string)
    Name of the processor used in ther meter configuration.

  - `data.operatorId` (string)
    ID of the processor used in the meter configuration.

  - `previousPage` (string)
    Cursor for the previous page of audit records, if available. Used for backward pagination.

  - `nextPage` (string)
    Cursor for the next page of audit records, if available. Used for forward pagination.

  - `error` (object)

  - `error.code` (string)
    Machine-readable error code identifying the failure type.

  - `error.message` (string)
    Human-readable description of the error that provides more context about what went wrong.

  - `error.detail` (object)
    Additional structured details about the error, such as validation issues or parameter-specific information.

## Response 400 fields (application/json):

  - `errors` (array)

  - `errors.code` (string)
    Machine-readable error code identifying the failure type.

  - `errors.message` (string)
    Human-readable description of the error that provides more context about what went wrong.

  - `success` (boolean)

## Response 500 fields (application/json):

  - `reasons` (array)
    Example: [{"code":"ObjectNotFound","message":"Notification definition with id 6e569e1e05f040eda51a927b140c0ac1 does not exist"}]

  - `reasons.code` (string)
    The error code of response.

  - `reasons.message` (string)
    The detail information of the error response