curl --request POST \
  --url https://mcp.zeroclick.ai/api/v1/analytics/metrics \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "startDate": "2026-01-01T00:00:00Z",
  "endDate": "2026-01-15T23:59:59Z"
}
'

{
  "data": [
    {
      "dimensions": {
        "tenantClientId": "<string>",
        "tenantGroupingId": "<string>"
      },
      "metadata": {
        "tenantClientName": "<string>"
      },
      "timeSeries": [
        {
          "prompts": 123,
          "eligiblePrompts": 123,
          "promptsWithMatchedAds": 123,
          "responsesWithImpressions": 123,
          "impressions": 123,
          "clicks": 123,
          "estimatedEarnings": 123,
          "datetime": "<string>",
          "date": "<string>"
        }
      ],
      "totals": {
        "prompts": 123,
        "eligiblePrompts": 123,
        "promptsWithMatchedAds": 123,
        "responsesWithImpressions": 123,
        "impressions": 123,
        "clicks": 123,
        "estimatedEarnings": 123
      }
    }
  ]
}

Deprecated

Get developer analytics metrics

deprecated

Deprecated. Sunset 2026-06-01. Use GET /api/v2/metrics instead.

After the sunset date this endpoint will return 410 Gone.

Migration notes:

Method changes from POST to GET; all body fields become query parameters.
startDate/endDate → startTime/endTime (still ISO 8601).
dimensions: ['HOURLY' | 'DAILY'] → granularity=hour | day (use /api/v2/metrics/geo for geo breakdown, no separate dimension required).
tenantClientIds: string[] (up to 100) → clientId (single value). Issue multiple requests if you need multiple clients.
tenantGroupingIds: string[] → groupingId (single value).
Auth header changes: send your Tenant API Key in the x-zc-api-key header instead of Authorization: Bearer <key>. The key value and required scope (developer:data:read) are unchanged. The related x-tenant-* headers are likewise renamed to x-zc-* (e.g. x-tenant-grouping-id → x-zc-grouping-id).

Returns aggregated ad performance metrics for your tenant over a time range.

Validation Rules:

startDate must be before or equal to endDate
HOURLY and DAILY dimensions are mutually exclusive
Maximum date range: 31 days for HOURLY, 365 days for DAILY or no time dimension
Maximum 100 items for tenantClientIds and tenantGroupingIds arrays

POST

api

analytics

metrics

curl --request POST \
  --url https://mcp.zeroclick.ai/api/v1/analytics/metrics \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "startDate": "2026-01-01T00:00:00Z",
  "endDate": "2026-01-15T23:59:59Z"
}
'

{
  "data": [
    {
      "dimensions": {
        "tenantClientId": "<string>",
        "tenantGroupingId": "<string>"
      },
      "metadata": {
        "tenantClientName": "<string>"
      },
      "timeSeries": [
        {
          "prompts": 123,
          "eligiblePrompts": 123,
          "promptsWithMatchedAds": 123,
          "responsesWithImpressions": 123,
          "impressions": 123,
          "clicks": 123,
          "estimatedEarnings": 123,
          "datetime": "<string>",
          "date": "<string>"
        }
      ],
      "totals": {
        "prompts": 123,
        "eligiblePrompts": 123,
        "promptsWithMatchedAds": 123,
        "responsesWithImpressions": 123,
        "impressions": 123,
        "clicks": 123,
        "estimatedEarnings": 123
      }
    }
  ]
}

Authorizations

Authorization

string

header

required

Legacy auth for the deprecated v1 endpoint. Tenant API Key with developer:data:read scope, sent as Authorization: Bearer <key>. v2 endpoints use the x-zc-api-key header instead.

Body

application/json

startDate

string

required

Start date in ISO 8601 format (e.g., "2026-01-01T00:00:00Z")

endDate

string

required

End date in ISO 8601 format (e.g., "2026-01-31T23:59:59Z")

dimensions

enum<string>[]

Dimensions to group by. Empty array returns overall aggregates. Can combine entity dimensions (TENANT_CLIENT_ID, TENANT_GROUPING_ID) with one time dimension (HOURLY or DAILY). Time dimensions are mutually exclusive.

Available options:

TENANT_CLIENT_ID,

TENANT_GROUPING_ID,

HOURLY,

DAILY

tenantClientIds

string[]

Optional filter by tenant client IDs (max 100 items)

tenantGroupingIds

string[]

Optional filter by tenant grouping IDs (max 100 items)

Response

Successful response with aggregated metrics and optional time series breakdown

Developer analytics metrics response

data

object[]

required

Array of groups, each containing dimension values, time series data, and totals

Show child attributes

Get a signal export job's status