You can use the Publisher Summary API to pull performance data. Learn how to generate performance data reports. 

Step 1: Create an API key in Publisher Portal

To create a new API key, click your user profile in the upper-right corner, select **API Key**, and then click Create API Key.

Copy the generated API key and store it securely. API keys generated in Publisher Portal begin with pp_. In the examples below, replace <your-api-key-here> with the complete API key, including the pp_ prefix. The ellipsis in the abbreviated format pp_... is not part of the API key.

Step 2: Generate a bearer token

Exchange your API key for a short-lived bearer token. After the API key has been created, generating a token does not require an email address, password, or an interactive sign-in to Publisher Portal.

curl --request POST \
  --url https://sdkpubapi.moloco.com/api/adcloud/publisher/v2/auth/tokens \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data @- <<EOF
{
  "api_key": "<your-api-key-here>"
}
EOF

Use the bearer token returned in the response to authenticate your Publisher Summary API requests.

Step 3: Make an API request for the Publisher Summary API endpoint.

Send a POST request to the following endpoint:

POST https://sdkpubapi.moloco.com/api/adcloud/publisher/v2/sdk/summary

Required properties

The following properties must be included in the request body.

"date_range": {
  "start": "YYYY-MM-DD",
  "end": "YYYY-MM-DD"
}

"dimension_filters": [
  {
    "dimension": "<DIMENSION_NAME>",
    "values": ["string"]
  }
]

"order_by": [
  {
    "dimension": "<DIMENSION_NAME>",
    "is_descending": true
  }
]

Available metrics

You must include one or more of the following metrics in the request body. 

Available dimensions

You must include one or more of the following dimensions in the request body.

YYYY-MM-DD HH:mm:SS +0000 UTC

Request body

The request body must be formatted as follows.

{
  "publisher_id": "<MOLOCO-PUBLISHER-ID>",
  "date_range": {
    "start": "YYYY-MM-DD",
    "end": "YYYY-MM-DD"
  },
  "dimensions": ["<DIMENSION_NAME>"],
  "metrics": ["<METRIC_NAME>"],
  "dimension_filters": [
    {
      "dimension": "<DIMENSION_NAME>",
      "values": ["string"]
    }
  ],
  "order_by": [
    {
      "dimension" | "metric": "<DIMENSION_NAME> | <METRIC_NAME>",
      "is_descending": true | false
    }
  ]
}

Include the bearer token generated in Step 2 in the Authorization header. In the request body, specify the Publisher ID, date range, dimensions, and metrics for the data you want to retrieve.

curl --request POST \
  --url https://sdkpubapi.moloco.com/api/adcloud/publisher/v2/sdk/summary \
  --header 'content-type: application/json' \
  --header 'Authorization: Bearer <your-token-here>' \
  --data @- <<EOF
{
  "publisher_id": "<your-publisher-id>",
  "date_range": {
    "start": "YYYY-MM-DD",
    "end": "YYYY-MM-DD"
  },
  "dimensions": ["UTC_DATE"],
  "metrics": ["REVENUE"]
}
EOF

Filter data

You can apply filter(s) to the data to retrieve only a subset of data. You can specify any of the available dimensions as filters as in the following example. 

{
  "publisher_id": "<your-publisher-id>",
  "date_range": {
    "start": "2026-06-10",
    "end": "2026-06-15"
  },
  "dimensions": ["UTC_DATE", "AD_UNIT_ID"],
  "metrics": ["REVENUE", "IMPRESSIONS"],
  "dimension_filters": [
    {
      "dimension": "PUBLISHER_APP_ID",
      "values": ["<moloco-app-id>"]
    },
    {
      "dimension": "GEO_COUNTRY",
      "values": ["USA", "CAN"]
    }
  ]
}

This sample request returns in the response the total revenue amount and total number of impressions from June 10, 2026 to June 15, 2026 from Canada and the US for an app with the App Key <moloco-app-id>, grouped by date and Ad Unit ID. 

Group and arrange data by one or more dimensions and/or metrics

You can group data by one or more of the available dimensions and/or metrics. The following sample request returns in the response the ad fill rate and total number of clicks by date and App Key, with date displayed from least to most recent and fill rate displayed from greatest to least.

{
  "publisher_id": "<your-publisher-id>",
  "date_range": {
    "start": "2026-06-10",
    "end": "2026-06-11"
  },
  "dimensions": ["UTC_DATE", "PUBLISHER_APP_ID"],
  "metrics": ["IMP_FILL_RATE", "CLICKS"],
  "order_by": [
    {
      "dimension": "TIME_BUCKET",
      "is_descending": false
    },
    {
      "metric": "IMP_FILL_RATE",
      "is_descending": true
    }
  ]
}

Response body

The response returned from the API request is formatted as follows. Only the dimensions and/or metrics specified in the API request are returned in the response.

{
  "rows": [
    {
      "utc_time_bucket": "YYYY-MM-DD",
      "app": {
        "app_id": "<moloco-app-id-in-inventory-sheet>",
        "app_title": "<pretty-app-name>"
      },
      "ad_unit": {
        "ad_unit_id": "<moloco-ad-unit-id-in-inventory-sheet>",
        "ad_unit_title": "<pretty-ad-unit-name>",
        "inventory_type": "BANNER" | "INTERSTITIAL" | "REWARDED",
        "bidfloor": string
      },
      "device": {
        "os": "IOS" | "ANDROID"
      },
      "geo": {
        "country": "<ISO 3166-1 alpha-3 country code>"
      },
      "metric": {
        "revenue": float64,
        "impressions": int64,
        "requests": int64,
        "clicks": int64,
        "ecpm": float64,
        "fill_rate": float64
      }
    }
  ]
}

Metrics

Dimensions

YYYY-MM-DD HH:MM:SS +0000 UTC

The following is a sample request for revenue amount by date and OS type from June 10 2026.

curl --request POST \
  --url https://sdkpubapi.moloco.com/api/adcloud/publisher/v2/sdk/summary \
  --header 'content-type: application/json' \
  --header 'Authorization: Bearer <your-token-here>' \
  --data @- <<EOF
{
"publisher_id": "<your-publisher-id>",
"date_range": {
"start": "2026-06-10",
"end": "2026-06-10"
},
"dimensions": ["UTC_DATE", "DEVICE_OS"],
"metrics": ["REVENUE"]
}
EOF

The response returned includes only the information that was requested.

{
  "rows": [
    {
      "utc_time_bucket": "2026-06-10 00:00:00 +0000 UTC",
      "device": {
        "os": "IOS"
      },
      "metric": {
        "revenue": 100.01
      }
    },
    {
      "utc_time_bucket": "2026-06-10 00:00:00 +0000 UTC",
      "device": {
        "os": "ANDROID"
      },
      "metric": {
        "revenue": 99.99
      }
    }
  ]
}

Timezones and availability

We use UTC timezone for pulling and displaying datasets. While most data is available in real time, it may take a couple of hours for some of the data to be made available. As a result, you can expect a full day's worth of data to be made available up to 6 hours past midnight UTC of the day data was recorded. 

Token expiration and renewal

The bearer token is valid for 16 hours. For recurring or scheduled reporting jobs:
Repeat Step 2 to generate a new token when needed
Do not hardcode or permanently store the short-lived bearer token.

Previous instructions

The previous authentication flow is described in the Moloco Publisher Summary API v1 (Legacy).