Sign in
Meters

Export details of a specific meter

The Export Meter operation exports the full definition of a specific meter in Zuora Mediation, including metadata, all versions, event schemas, and operator configurations (source, processor, sink). It's useful for reviewing, backing up, or replicating meter setups across environments.

get/meters/export/{meterId}

Path parameters

meterIdstring required

ID of the meter to export.

Headers

Content-Typestring required

Specify the content type of the request body. Use application/json.

Accept-Encodingstring

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-Encodingstring

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-Idsstring

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-Idsstring

Comma separated IDs. If you have <a href="https://docs.zuora.com/en/zuora-platform/organization-and-entity-management/multi-org/overview-of-multi-org" target="_blank">Zuora Multi-Org</a> 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-Idstring

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

Successful response with meter export data

namestring

Meter name

descriptionstring

Meter description

typestring

Meter type (e.g., CUSTOM, STANDARD)

latestVersionstring

The latest version of the meter

Example response

{
  "schemas": [
    {
      "name": "source(97)",
      "type": 1,
      "schema": {
        "description": "A description",
        "type": "object",
        "title": "source",
        "required": [
          "CustomerId",
          "UsageIdentifier",
          "UsageDate"
        ],
        "properties": {
          "Amount": {
            "type": "number",
            "description": "Amount"
          },
          "Quantity": {
            "type": "number",
            "description": "Quantity"
          },
          "UsageDate": {
            "type": "string",
            "description": "UsageDate"
          },
          "CostCenter": {
            "type": "string",
            "description": "CostCenter"
          },
          "CustomerId": {
            "type": "string",
            "description": "CustomerId"
          },
          "UsageIdentifier": {
            "type": "string",
            "description": "UsageIdentifier"
          }
        }
      }
    }
  ]
}

Changes

No recorded changes to this endpoint across all 4 revisions of this API.