Changelog

CloudX API release history

2026-10-13

Reporting timezone parameter

The reporting API adds an optional timezone query parameter to GET /report/dashboard, GET /report/apps, GET /report/ad-units, GET /report/bidders, GET /report/breakdown, and GET /report/ab-test. Use an IANA timezone such as America/New_York. Omitting the parameter preserves UTC behavior and existing response formats.

start_time and end_time remain absolute Unix timestamps in seconds and are never shifted. For calendar-date requests, callers must first convert their local boundaries to these timestamps; CLI 0.41 does this with --timezone. Dashboard and breakdown calendar buckets then follow the selected timezone. Dashboard date and day/week/month labels use local dates; bucket_start and hourly breakdown keys remain UTC RFC 3339 instants so repeated daylight-saving hours stay distinct.

Unsupported timezones return 400 Bad Request. SDK reports, hourly dashboard/breakdown reports, and breakdowns grouped by bidder require whole-hour offsets throughout the requested window. A/B reports support UTC only. Existing date-range limits, export behavior, and Demand Comparison’s timezone and completion rules remain unchanged.

2026-10-09

Network report path

GET /reports/network moved to GET /report/network. It now sits under /report/* with the other reporting endpoints. Parameters, responses, and the reports:read permission do not change.

Breaking Changes

• GET /reports/network returns 404 Not Found. The old path has no alias or redirect. Update every caller to GET /report/network.

2026-09-30

Demand Comparison date ranges

Both Demand Comparison endpoints now accept inclusive calendar-date windows of any length within available history. The start date remains on or after 2020-01-01. The end date must be complete under the 12:00 UTC cutoff. Some requested dates may have no CloudX or partner data. Other reporting endpoints retain their existing date-range limits.

2026-09-15

Demand Comparison reporting

The public API now exposes Demand Comparison summary and ad-unit reports for accounts with feature access and the reports:read permission.

• GET /report/demand-comparison compares CloudX and partner revenue, eCPM, and impressions. It also reports matched CloudX ad units, mapping gaps, and partner report freshness.
• GET /report/demand-comparison/ad-units returns mapped partner aggregates by default. Set view=unmapped to return partner rows excluded because mappings are missing or ambiguous, with excluded_partner_revenue and excluded_partner_impressions.
• Demand-source filters use repeated query parameters. Provider business, provider property, and CloudX ad-unit filters accept comma-separated values.
• The most recent completed date changes at 12:00 UTC.

Read the CLI reporting guide →

2026-09-14

Bidder breakdown reporting

GET /report/breakdown accepts bidder as a by dimension for periods beginning on or after June 1, 2026. Combine it with app, format, and ad_unit to retrieve bidder-level bid requests, fills, impressions, revenue, clicks, and rates. requests remains the ad request count and repeats across bidder rows; use bid_requests for requests sent to each bidder.

2026-08-12

Activity exports

The public API now supports asynchronous, full-day impression, request, and bid activity exports.

Added

• Unified export endpoints — Create or reuse exports with POST /export/impressions, POST /export/requests, and POST /export/bids, then poll the matching GET endpoint for status and a short-lived download URL.
• Request and bid activity — Request exports include auction outcomes and bidder-funnel fields. Bid exports include bids, no-bids, timeouts, and errors, with losing prices redacted. Request export docs → Bid export docs →

2026-05-29

Configuration writes

The public API now exposes typed config write operations through POST /config/edit for apps, ad units, ad unit groups, lists, tags, test devices, network mappings, line items, and A/B tests.

2026-05-15

Public API release

CloudX now has a public API for programmatic access to reporting, auction inspection, and account configuration data. The API uses CloudX API keys as bearer tokens and is documented with an interactive OpenAPI reference. Read the docs →

Added

• Reporting endpoints — Retrieve dashboard summaries, breakdown rows, bidder performance, app performance, ad-unit performance, and CSV-style exports.
• Auction inspection endpoints — Inspect auctions, rounds, bids, ILRD rows, and related delivery details.
• Configuration endpoints — Read live, draft, and published account configuration, including configuration history.