# Run a specific version of a meter

Executes a specific version of a meter in Zuora Mediation. You can choose to run it with either a local file or event store source by providing optional configurations.

Endpoint: POST /meters/run/{meterId}/{version}
Version: 2026-02-20
Security: bearerAuth

## Path parameters:

  - `meterId` (string, required)
    The ID of the meter to run.

  - `version` (string, required)
    The version of the meter to run.

## 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 (').

## Request fields (application/json):

  - `sourceOptions` (array)
    Settings for meter to run with local file.

  - `sourceOptions.processorId` (string)
    Source operator ID. Optional if there's only one local file source in the meter.

  - `sourceOptions.localFileId` (string)
    Internal ID of uploaded file.

  - `eventStoreSourceOptions` (array)
    Settings for meter to run with event store.

  - `eventStoreSourceOptions.processorId` (string, required)
    Source operator ID.

  - `eventStoreSourceOptions.startDate` (string)
    Start date of event store to query from (e.g., 2025-01-01).

  - `eventStoreSourceOptions.endDate` (string)
    End date of event store to query to (e.g., 2025-02-01).

## Response 200 fields (application/json):

  - `success` (boolean)
    Whether the API request has succeeded.

  - `data` (object)

  - `data.id` (string)
    Internal run history ID, unique within tenant.

  - `data.sessionId` (string)
    Corresponding session ID of this run.

  - `data.jobId` (string)
    Corresponding job ID of this run.

  - `data.meterId` (integer)
    Internal meter ID.

  - `data.version` (string)
    Version of the meter.

  - `data.revision` (integer)
    Revision number of this version run.

  - `data.runType` (integer)
    The run type:
- 1. NORMAL
- 2. DEBUG

  - `data.runTypeDescription` (string)
    Description of the run type.

  - `data.startTime` (string)
    Start time of this run.

  - `data.endTime` (string,null)
    End time of this run.

  - `data.status` (integer)
    The run status:
- 1. NEVER_RUN
- 2. TESTING
- 3. TESTING_FAILED
- 4. TESTING_PASSED
- 5. RUNNING
- 6. PAUSED
- 7. COMPLETED
- 8. FAILED
- 9. CANCELED
- 10. INITIALIZING
- 11. USAGE_PUSHING
- 12. PUSH_COMPLETED
- 13. CONSUME_COMPLETED

  - `data.statusDescription` (string)
    Description of the run status.

  - `data.canExportSummary` (boolean)
    Whether the summary is ready to export.

  - `data.hasLineageEnabled` (boolean)
    Whether lineage feature is enabled on this run.

## 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 401 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