DoubleVerify API

Name: DoubleVerify API API
Brand: DoubleVerify API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness IntelligenceapiKey9 EndpointsREST

For Agents

Pull DoubleVerify campaign metrics, advertiser metadata, and verification reports so an agent can monitor brand safety and viewability for digital advertising.

Quickstart

Get started with DoubleVerify 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:
"get DoubleVerify campaign metrics"

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

Capabilities

What an agent can do with DoubleVerify API API.

List campaigns visible to the authenticated DoubleVerify account

Retrieve viewability and brand safety metrics for a specific campaign

Create a verification report job and poll for completion

Download a generated verification report file once it is ready

List advertisers and pull individual advertiser metadata

GET STARTED

Start building with DoubleVerify API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for DoubleVerify API, keeping it validated and agent-ready. DoubleVerify provides digital advertising verification — measuring viewability, brand safety, fraud, and audience accuracy across digital campaigns. The API exposes campaign listing and metrics, advertiser metadata, and a reporting subsystem that can create, list, and download verification reports. Authentication uses an Authorization header API key, suitable for scheduled reporting jobs and automated campaign monitoring.

Use Cases

Patterns agents use DoubleVerify API API for, with concrete tasks.

★ Daily Brand Safety Monitoring

Pull campaign-level brand safety and viewability metrics from DoubleVerify each morning to flag any campaign with degraded scores. The agent lists campaigns via GET /campaigns, then iterates GET /campaigns/{campaignId}/metrics to compare against thresholds. Issues are escalated to the trading team before the day's spend ramps up.

List campaigns via GET /campaigns, fetch metrics for each via GET /campaigns/{campaignId}/metrics, and report any campaign with viewability below 60%.

Scheduled Verification Reporting

Create scheduled DoubleVerify reports, wait for them to render, and download the file to a shared analytics warehouse. The agent calls POST /reports to start the job, polls GET /reports/{reportId} until status is ready, then downloads via GET /reports/{reportId}/download. This automates a workflow that brand safety teams typically run by hand each week.

Create a weekly verification report via POST /reports, poll GET /reports/{reportId} until ready, and download the file via GET /reports/{reportId}/download into S3.

Advertiser Onboarding Audit

When onboarding a new advertiser, list current advertisers via GET /advertisers and pull each via GET /advertisers/{advertiserId} to confirm metadata and access scope. This sanity check catches missing or duplicated advertiser records before campaigns are mapped, avoiding measurement gaps later in the quarter.

List advertisers via GET /advertisers and fetch GET /advertisers/{advertiserId} for any new entry to confirm the metadata is complete.

AI Agent Verification Insights

Through Jentic, an AI agent can take 'how did our display campaigns perform on viewability last week' and resolve it to the DoubleVerify campaigns and metrics endpoints without browsing docs. Jentic injects the API key from the vault and validates the campaign id parameter. End-to-end setup is under an hour from sign-up.

Use Jentic search for 'get DoubleVerify campaign metrics', load the /campaigns/{campaignId}/metrics operation, and execute it for campaign id 'CMP-1024'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/campaigns

List campaigns

GET

/campaigns/{campaignId}/metrics

Get campaign metrics

POST

/reports

Create a verification report

GET

/reports/{reportId}

Get report status

GET

/reports/{reportId}/download

Download a report

GET

/advertisers

List advertisers

GET

/advertisers/{advertiserId}

Get advertiser metadata

GET

/campaigns

List campaigns

GET

/campaigns/{campaignId}/metrics

Get campaign metrics

POST

/reports

Create a verification report

GET

/reports/{reportId}

Get report status

GET

/reports/{reportId}/download

Download a report

GET

Why though Jentic?

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

Credential isolation

DoubleVerify API keys are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents receive a scoped reference, never the raw key.

Intent-based discovery

Agents search by intent (e.g. 'get DoubleVerify campaign metrics') and Jentic returns the matching campaigns or reports operation with its input schema, so the agent calls the right endpoint without reading docs.

Time to first call

Direct DoubleVerify integration: 1-2 days for auth, report polling, and download handling. Through Jentic: under an hour from sign-up to first metrics pull.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Drive API

Drop downloaded DoubleVerify report files into Drive for sharing across the trading team.

Use Drive when the report needs to be shared with non-technical stakeholders. Use DoubleVerify to generate the underlying report file.

Complementary

Facebook Graph API

Facebook Graph runs the campaign delivery; DoubleVerify measures viewability and brand safety on the same inventory.

Use Facebook Graph to manage the campaigns themselves. Use DoubleVerify to verify how that delivery performed against viewability standards.

Complementary

Monday.com API

Push DoubleVerify alerts as items into a Monday board so the brand-safety team has a single inbox.

Use Monday when alerts need ticketing and ownership. Use DoubleVerify to source the underlying brand-safety signal.

FAQs

Specific to using DoubleVerify API API through Jentic.

Why is there no official OpenAPI spec for DoubleVerify API?

DoubleVerify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DoubleVerify API 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 DoubleVerify API use?

DoubleVerify uses an API key passed in the Authorization request header. Through Jentic, that key is stored encrypted in the vault and injected at execution time, so it never appears in the agent's context.

Can I pull campaign-level brand safety metrics?

Yes. GET /campaigns/{campaignId}/metrics returns viewability and brand safety figures for the specified campaign. Use GET /campaigns first to discover campaign ids visible to the authenticated account.

How do I generate a verification report through Jentic?

Run pip install jentic, search for 'create a DoubleVerify report', load the POST /reports operation, and execute it with the report parameters. Then poll GET /reports/{reportId} until status is ready and download via GET /reports/{reportId}/download.

Can I list advertisers programmatically?

Yes. GET /advertisers returns the advertisers visible to the authenticated account, and GET /advertisers/{advertiserId} returns metadata for a specific advertiser.

What are the rate limits for the DoubleVerify API?

The published spec does not declare explicit per-endpoint limits. Build retry-with-backoff into reporting jobs and treat 429 responses as the signal to slow down. Confirm production thresholds with DoubleVerify directly.