Native Ads Publisher API
Browse all Nativeads APIs★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingbearer4 EndpointsREST
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 the Jentic vault 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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Native Ads publisher email and password are stored encrypted in the Jentic vault. Jentic performs the /auth/default/login call to obtain a session token and injects it into subsequent reporting requests, so the agent never sees the raw password.
Intent-based discovery
Agents search Jentic by intent (e.g. 'pull Native Ads publisher revenue report') and Jentic returns the matching reporting operation with its input schema for direct execution.
Time to first call
Direct integration with Native Ads: 1-2 days for login flow, token caching, and report parsing. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Native Ads Publisher API
Equivalent Native Ads publisher spec sourced from a different OpenAPI revision in the catalogue.
Use the alternate slug if the agent already targets that path in the catalogue; both expose the same publisher endpoints.
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. Sign up at https://app.jentic.com/sign-up.
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.
GET STARTED