Reporting API

description: Access your revenue, traffic, and performance data programmatically via the Panxo Reporting API.

Reporting API

The Reporting API gives publishers programmatic access to their revenue and traffic data. Use it to build custom dashboards, automate reporting, or integrate Panxo metrics into your existing analytics stack.


Authentication

All requests require an API key passed via the X-Panxo-API-Key header.

curl -X GET https://api.panxo.com/api/v1/reporting/overview \
  -H "X-Panxo-API-Key: pk_your_api_key_here"

Getting your API key

2

Open API Keys

Go to Settings > API Keys

3

Generate

Generate a new key (format: pk_...)

circle-exclamation

Base URL

https://api.panxo.com/api/v1/reporting

Endpoints

GET /overview

Returns aggregated metrics for your property over a given period.

Query Parameters

Parameter
Type
Required
Default
Description

period

string

No

30d

Time period. One of: 7d, 30d, 90d

Request

Response

Response Fields

Field
Type
Description

revenue.total

number

Total revenue in USD for the period

revenue.currency

string

Always USD

traffic.ai_visits

number

Total AI-influenced visits

traffic.human_visits

number

Total human visits

traffic.ai_percentage

number

AI visits as percentage of total traffic

performance.rpm

number

Average Revenue Per Mille (per 1,000 AI visits)

performance.fill_rate

number

Average fill rate (percentage of AI visits that received an ad)


GET /daily

Returns a day-by-day breakdown of revenue and traffic metrics.

Query Parameters

Parameter
Type
Required
Default
Description

days

number

No

30

Number of days to return. Range: 1-90

Request

Response

Response Fields (per day)

Field
Type
Description

date

string

Date in YYYY-MM-DD format

revenue

number

Revenue in USD for that day

ai_visits

number

AI-influenced visits

human_visits

number

Human visits

rpm

number

RPM for that day

fill_rate

number

Fill rate for that day

circle-info

Data is ordered by date descending (most recent first). Days with no traffic data are omitted from the response.


Error Handling

Authentication Errors

HTTP Code
Error
Cause

401

Authentication required

Missing X-Panxo-API-Key header

401

Invalid API key format

Key does not start with pk_

403

Invalid or inactive API key

Key not found or property is inactive

429

Rate limit exceeded

Too many requests

500

Failed to fetch overview data

Internal server error

Response Structure

All responses follow the same structure:

Success:

Error:


Rate Limits

Limit
Value

Requests per minute

60

Requests per day

10,000

Rate limit headers are included in responses:


Code Examples


Support

Resource
Link

Last updated