The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are ReportingTotalsMetrics (15 properties), ReportingMetrics (15 properties), TimeseriesEntry (14 properties), StorefrontTimeseriesEntry (12 properties). Each schema is shown below with its type and property counts.
MediaBuyReporting
object
Media buy-level reporting metrics with package breakdown
7 properties6 required
EventSummaryResponse
object
Response containing hourly-aggregated event counts for an advertiser
4 properties4 required
EventSummaryEntry
object
A single hourly aggregation entry
3 properties3 required
TimeseriesEntry
object
One row of metrics for a single (advertiser → campaign → media buy → package) leaf on a single day
14 properties14 required
CampaignReporting
object
Campaign-level reporting metrics with media buy breakdown
5 properties5 required
ReportingConversionInfo
object
How the consolidated (FX-converted) figures were produced
7 properties7 required
AdvertiserReporting
object
Advertiser-level reporting metrics with campaign breakdown
5 properties5 required
ConsolidatedReporting
object
FX-converted cross-advertiser rollup (display estimate only — never billing)
3 properties3 required
ErrorResponse
object
Standard error response
2 properties2 required
ReportingMetricsExportResponse
object
Response containing a signed URL to download the exported CSV
4 properties4 required
ApiError
object
Structured error object
4 properties2 required
PackageReporting
object
Package-level reporting metrics
4 properties4 required
EventSummaryType
string
Type of event to filter by: conversion, click, impression, measurement, or mmp
ReportingTotalsMetrics
object
Reporting totals; money metrics are null when returned denominations mix or no denomination is available
Whether the platform acts on this campaign. "tracked" = a campaign the platform did not set up, mirrored from a connected seller account: the shell is derived…
ReportingMetricsTimeseriesResponse
object
Time-series reporting response: flat leaf × day rows (same hierarchy fields as the summary view, plus date)
5 properties5 required
StorefrontReportingMetricsTimeseriesResponse
object
Time-series storefront reporting response: flat leaf × day rows
4 properties4 required
SettlementStatus
string
Per-edge settlement state: booked (committed, no delivery yet), accruing (delivering), settled (final), void (cancelled — excluded from this report).
StorefrontAdvertiserReporting
object
Advertiser-level reporting metrics with media buy breakdown (no campaign level)
4 properties4 required
MarginBuyer
object
Buyer-level P&L with media-buy breakdown
4 properties4 required
MarginAmounts
object
Booked vs realized buy/sell/spread and margin %, one currency. The buy/sell/spread figures are independent coverage sums (each over the legs that carry that fi…
11 properties11 required
StorefrontPackageReporting
object
Package-level reporting metrics
4 properties4 required
StorefrontReportingMetricsResponse
object
Hierarchical storefront reporting response: advertiser → media buy → package
4 properties4 required
StorefrontTimeseriesEntry
object
One row of metrics for a single (advertiser → media buy → package) leaf on a single day
12 properties12 required
MarginMediaBuy
object
Media-buy-level P&L with package breakdown
3 properties3 required
StorefrontMediaBuyReporting
object
Media buy-level reporting metrics with package breakdown
7 properties7 required
StorefrontMarginReportingResponse
object
Hierarchical storefront margin (P&L) response: buyer → media buy → package → source leg
4 properties4 required
MarginSourceLeg
object
One buy-leg edge: a single source package under a buyer package
5 properties5 required
MarginPackage
object
Package-level P&L with per-source-leg breakdown. Package amounts are the sum of the source legs; this reconciles only while each buyer package routes to a sing…
4 properties4 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Scope3 Reporting API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
