Anura Reporting API

Name: Anura Reporting API API
Brand: Anura Reporting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsWeb AnalyticsapiKey11 EndpointsREST

For Agents

Pull ad-fraud session, browser, geography, and network reports from Anura across Direct, Script, and Interface modes. Suited to dashboard, alerting, and review agents that surface fraud signals.

Quickstart

Get started with Anura Reporting API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pull Anura session report for last 7 days"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Anura Reporting API API.

Pull session-count breakdowns by Direct, Script, and Interface integration modes for a date window

Read browser distribution reports to spot anomalous user-agent concentrations

Retrieve geography reports showing session counts and fraud rates by country or region

Query network reports to identify suspicious ASNs or hosting-provider traffic

GET STARTED

Start building with Anura Reporting API API

Explore with Jentic

View OpenAPI Document

Use for: Get session counts for the last 7 days from my Anura Script integration, List all Anura instances configured on my account, Retrieve the geography breakdown for Direct traffic yesterday, Find the top ASNs by session count in the last week

Not supported: Does not perform request-time fraud scoring, ad serving, or campaign management — use for retrieving Anura session, browser, geography, and network reports only.

Jentic publishes the only available OpenAPI document for Anura Reporting API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Anura Reporting API, keeping it validated and agent-ready. Anura is an ad-fraud detection service whose Reporting API exposes 11 POST endpoints for pulling session, browser, geography, and network breakdowns split across Direct, Script, and Interface integration modes. Agents can query short-window session reports (a 7-day rolling frame, or 31 days for Overview-style endpoints) to drive dashboards and alerting on suspicious traffic. Authentication uses the token query parameter on every request.

Use Cases

Patterns agents use Anura Reporting API API for, with concrete tasks.

★ Daily Fraud Review Dashboard

Build a daily dashboard that pulls session, geography, and network reports for the past 7 days from POST /script/sessions, /script/geography, and /script/networks and renders fraud-rate trends per source. Anura returns counts split by suspicious, warning, and good classifications, so the dashboard can highlight the campaigns or geos driving the day's fraud spike without exposing raw event-level data.

Call POST /script/sessions, /script/geography, and /script/networks for the last 7 days, then aggregate the suspicious counts per source for the dashboard

Campaign-Level Fraud Alerting

Watch a campaign by polling POST /interface/campaigns alongside the Interface session and network endpoints, raising an alert when the suspicious rate exceeds a threshold. Because Anura caps date-specific queries at a 7-day rolling window (31 days for Overview), the agent runs short, frequent polls rather than long historical pulls — which suits a streaming alert pipeline.

Call POST /interface/campaigns to list active campaigns, then for each call POST /script/sessions for the last hour and trigger an alert if the suspicious rate exceeds 5 percent

Source and Instance Inventory

Maintain a configuration catalogue of every Anura instance, source, and campaign by listing them via POST /interface/instances, /interface/sources, and /interface/campaigns. The agent uses this to validate that a downstream system's source IDs match Anura's records and to scope subsequent Direct or Script reporting calls without hard-coding identifiers.

Call POST /interface/instances, then POST /interface/sources and /interface/campaigns and persist the returned IDs as the canonical configuration list

AI Agent Fraud Reporting via Jentic

An AI agent that triages ad-fraud incidents can pull Anura reports through Jentic without managing the token query parameter directly. Jentic's intent search routes the agent to the right /script, /direct, or /interface endpoint with its parameter schema, and the token is loaded from the vault at execution time so it never enters the agent's tool context.

Search Jentic for 'pull Anura session report for last 7 days', load POST /script/sessions, and execute with the Script source ID and date window

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for anura reporting api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/script/sessions

Session-count report for the Script integration

POST

/script/geography

Geography breakdown for the Script integration

POST

/script/networks

Network breakdown for the Script integration

POST

/script/browsers

Browser breakdown for the Script integration

POST

/direct/sessions

Session-count report for the Direct integration

POST

/interface/instances

List configured Anura instances

POST

/interface/sources

List configured sources

POST

/interface/campaigns

List configured campaigns

POST

/script/sessions

Session-count report for the Script integration

POST

/script/geography

Geography breakdown for the Script integration

POST

/script/networks

Network breakdown for the Script integration

POST

/script/browsers

Browser breakdown for the Script integration

POST

/direct/sessions

Session-count report for the Direct integration

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Anura tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the token query parameter is reconstructed at execution time so the raw token never enters the agent's prompt or tool context, which matters because the token grants read access to sensitive fraud reporting.

Intent-based discovery

Agents search by intent (e.g., 'pull Anura session report for last 7 days') and Jentic returns POST /script/sessions or the equivalent /direct or /interface endpoint with its filter schema, so the agent does not have to map between Direct, Script, and Interface modes from the docs.

Time to first call

Direct Anura integration: 1 day to wire token auth, mode-specific endpoints, and 7-day window handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Fingerprint API

Fingerprint detects device-level fraud signals at request time rather than reporting on aggregated sessions.

Choose Fingerprint when the agent needs real-time device-trust signals during a request rather than after-the-fact reporting.

Alternative

Sift API

Sift offers fraud detection across payments, accounts, and content with both scoring and reporting endpoints.

Choose Sift when the agent needs broader fraud coverage spanning payments and account abuse alongside ad fraud.

Complementary

MaxMind API

MaxMind provides IP intelligence and minFraud scoring that complements Anura's session reports.

Choose MaxMind when the agent needs IP-level reputation data to enrich the network breakdowns Anura reports.

FAQs

Specific to using Anura Reporting API API through Jentic.

Why is there no official OpenAPI spec for Anura Reporting API?

Anura publishes its reporting docs at docs.anura.io as HTML reference rather than a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Anura via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Anura Reporting API use?

Anura uses an API token sent as a query parameter named token on every request. Through Jentic the token is stored in the encrypted vault and injected at execution time, so the raw token never enters the agent's prompt context.

Can I pull session reports for arbitrary date ranges from Anura?

No. Date-specific reports are limited to a 7-day rolling time frame, except Overview endpoints which extend to 31 days. Schedule daily or hourly poll jobs that stay inside the rolling window rather than requesting long historical ranges.

What are the rate limits for the Anura Reporting API?

The OpenAPI spec does not declare explicit rate limits. Anura caps every report to a 7-day window (31 days for Overview) which naturally bounds traffic, but you should still back off on 429 responses and avoid running every endpoint in parallel for every source.

How do I pull a daily session report from Anura through Jentic?

Run pip install jentic, then search Jentic for 'pull Anura session report for last 7 days'. Jentic returns POST /script/sessions with its filter schema. Execute with your Script source ID and the desired date range; the token is injected from the vault.

Why are all Anura endpoints POST instead of GET?

Anura models report parameters (date range, source, instance, classification filters) as a JSON body rather than query strings, so every reporting endpoint uses POST. Only the token authentication value is sent as a query parameter.