A client-supplied unique identifier used to correlate request and response pairs across /meter/v2/apis/requests and /meter/v2/apis/response endpoints. Must be consistent between related API calls to ensure proper usage tracking and analytics.

Sources are typically individual API endpoints. For existing sources, the ID can be found in the Revenium platform on the sources page or retrieved programmatically via the list sources endpoint. A sourceId is created automatically for new sources.

The credential used to access the API (e.g., API key, OAuth token, or key alias). This identifier maps the API transaction to a specific subscriber and their associated subscription/product for proper usage tracking and billing. Visible on the subscriber credentials page in the Revenium platform. Credentials can be API keys or key aliases depending on your system architecture.

Specifies the originating platform or gateway of the metered API traffic. This helps Revenium properly process and categorize incoming metrics according to their source system architecture. If not specified, defaults to 'UNKNOWN'.

The HTTP method of the request

        Visible in the ‘resource’ field when viewing sources in the revenium application. 
        The resource field (often a full URL or relative URI) can be used to auto-match 
        transactions to existing sources based on the URL/URI accessed in the API call.
    

The content type of the request

The IP address for the origin of the request. Used by Revenium to report API usage by geography.

The user agent of the request