Native Ads Publisher API
Browse all Nativeads APIs62
AI ReadinessAI-Aware (B-)62/100
Community OpenAPI document · agent-readyMarketingAdvertisingbearer4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Authenticate to the Native Ads publisher account and pull daily, per-website, and per-widget revenue and performance reports.
Use for: Get the daily Native Ads publisher revenue report for last week, Retrieve per-website revenue from my Native Ads publisher account, Check Native Ads earnings broken down by widget, I want to log in to Native Ads and pull a session token
Not supported: Does not handle ad campaign creation, creative management, or advertiser billing - use for publisher-side revenue and engagement reporting only.
The Native Ads Publisher API exposes the reporting capabilities of the Native Ads publisher dashboard as a programmatic interface. Publishers can authenticate, then pull daily performance reports broken down by website or by individual ad widget for monetisation analytics. It is a small reporting-focused surface intended to mirror the GUI rather than to manage campaigns or creatives.
Install Jentic One Beta
Connect the Native Ads Publisher API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Native Ads Publisher API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnativeads.com%2Fnativeads-publisher" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnativeads.com%2Fnativeads-publisher" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Native Ads Publisher API.
Authenticate a publisher session with email and password to obtain a bearer token
Pull daily Native Ads publisher revenue reports for a chosen date range
Break down publisher revenue by website to compare property performance
Break down publisher revenue by ad widget for placement-level analysis
Feed Native Ads earnings into business intelligence dashboards alongside other ad networks
Use Cases
Patterns agents use Native Ads Publisher API for, with concrete tasks.
★ Daily Publisher Revenue Reporting
Publishers running Native Ads alongside other monetisation networks need a daily revenue feed for finance and operations dashboards. The /publisher/reports/daily endpoint returns aggregate revenue, impressions, and clicks per day after a login session is established. The result drops directly into a data warehouse table for trend analysis without scraping the publisher GUI.
Authenticate with /auth/default/login, then call /publisher/reports/daily for the last 30 days and return aggregate revenue and impressions per day.
Multi-Site Publisher Portfolio Analysis
Publishers operating multiple websites need to compare Native Ads performance per property to decide where to invest editorial effort. The /publisher/reports/website endpoint groups metrics by website ID, returning revenue, impressions, and click counts that feed directly into a portfolio dashboard. This replaces manual export from the publisher GUI for routine reviews.
Call /publisher/reports/website for the previous calendar month and return a sorted list of websites by revenue.
Widget-Level Placement Optimisation
Native Ads publishers run multiple widget placements per page and need widget-level revenue data to optimise layout. The /publisher/reports/widget endpoint returns per-widget revenue and engagement metrics, surfacing under-performing placements that could be retired or repositioned. Iterating on placements with this feed shortens the optimisation loop versus the dashboard view.
Pull /publisher/reports/widget for the last 14 days and flag any widget whose revenue dropped more than 20 percent week over week.
Agent-Driven Monetisation Reporting via Jentic
Operations agents that consolidate ad-network earnings into a finance system need a single entry point for Native Ads data. Through Jentic the agent searches by intent, loads the schema for the publisher reporting operations, and executes them, with credentials held in your Jentic One instance rather than in agent memory. The reporting JSON is then forwarded into the finance system without bespoke scraping logic.
Search Jentic for 'pull Native Ads publisher revenue report', load the schema for /publisher/reports/daily, and execute it for the previous calendar week.
Key Endpoints
4 endpoints — the native ads publisher api exposes the reporting capabilities of the native ads publisher dashboard as a programmatic interface.
METHOD
PATH
DESCRIPTION
POST
/auth/default/login
Log in with publisher credentials and return a session token
GET
/publisher/reports/daily
Return daily aggregate revenue and engagement metrics
GET
/publisher/reports/website
Return revenue and engagement metrics by website
GET
/publisher/reports/widget
Return revenue and engagement metrics by ad widget
POST
/auth/default/login
Log in with publisher credentials and return a session token
GET
/publisher/reports/daily
Return daily aggregate revenue and engagement metrics
GET
/publisher/reports/website
Return revenue and engagement metrics by website
GET
/publisher/reports/widget
Return revenue and engagement metrics by ad widget
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
N
Native Ads Publisher API
- AI-Aware (B-)62/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility32
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
32
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Native Ads by hand means running the /auth/default/login call to exchange your publisher email and password for a session token on the api.nativeads.com host, then attaching that token to every reporting request yourself. Through Jentic you install once, import the Native Ads Publisher API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Native Ads passes its reporting filters in the query rather than in the URL path, so scope the agent to the operations it needs, such as the daily and website revenue reports. You choose the operations it may call, so the widget report or the login call are not included unless you add them.
Credential isolation
Your Native Ads publisher email and password are stored once, encrypted, by your own Jentic One instance, which runs the login exchange and injects the session token at execution time. The raw password never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'pull the Native Ads publisher revenue report', and Jentic returns the matching reporting operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Native Ads Publisher API through Jentic.
What authentication does the Native Ads Publisher API use?
Authentication is a two-step flow. POST publisher email and password to /auth/default/login to receive a session token, then pass that token on subsequent reporting calls. Jentic stores the credentials in its vault and performs the login on the agent's behalf.
Can I get daily revenue reports with the Native Ads Publisher API?
Yes. After login, GET /publisher/reports/daily returns the publisher's aggregate daily revenue, impressions, and click metrics for the requested date range, mirroring the daily report in the publisher GUI.
What are the rate limits for the Native Ads Publisher API?
The OpenAPI spec does not publish rate limits for the Native Ads Publisher API. Rate-limit behaviour is governed by the publisher account; contact Native Ads support before running high-frequency batch jobs.
How do I pull a Native Ads revenue report through Jentic?
Run pip install jentic, search for 'pull Native Ads publisher revenue report', load the schema for /publisher/reports/daily, and execute it after Jentic has handled the /auth/default/login step. Run it through Jentic One, the self-hosted execution layer.
Does this API let me create or manage ad campaigns?
No. The Native Ads Publisher API is reporting-only. Creating campaigns, creatives, or budgets must be done through the Native Ads advertiser surface, which is a separate product not covered by this spec.
Can I limit what my agent is allowed to do with the Native Ads Publisher API?
Yes. Because you run Jentic One yourself, you decide which operations the agent may call, so you can grant only the reports it needs, such as the daily and per-website revenue reports, and leave out the widget report or the login call. The reporting filters are passed in the query rather than the URL path, so scoping is done at the operation level by the rules you set. Your publisher email and password are held by your own Jentic One instance, which runs the /auth/default/login exchange and injects the session token at execution time, so the agent never sees the raw credentials.
GET STARTED