RevContent
RevContent is a performance-driven native advertising and content recommendation network offering a REST API for managing widgets, campaigns (boosts), ad content, audience targeting, bidding, conversion pixels, sub accounts, and performance reporting. Publishers and advertisers access the platform through OAuth 2.0 client-credentials authenticated endpoints to programmatically control campaign settings, device, OS, browser, language and geo targeting, widget blacklisting, content delivery, and statistical reporting at scale. RevContent publishes its machine-readable contract as apiDoc rather than OpenAPI, at https://api.revcontent.io/docs/stats/api_data.json, covering 43 operations across eleven groups.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles RevContent the way a machine reads it — 62 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — RevContent scores 46.6/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from RevContent's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/revcontent/"
title="RevContent on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/revcontent.svg"
alt="RevContent Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/revcontent/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/revcontent/"
title="RevContent on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/revcontent/card.svg"
alt="RevContent Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile RevContent
Each block below is one kind of artifact we hold for RevContent. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
RevContent Stats & Management API
REST API providing programmatic access to RevContent's advertising platform for managing campaigns (boosts), widgets, content, targeting, widget blacklisting, conversion pixels,...
RevContent Access API
OAuth 2.0 client-credentials token issuance and account reactivation.
RevContent CCPA API
CCPA consumer data access and deletion requests for publishers.
RevContent Content API
Ad creatives attached to campaigns, and their per-widget performance.
RevContent Conversions API
Conversion pixel management used by CPA-optimized campaigns.
RevContent Helpers API
Reference lookups for browsers, countries, devices, DMAs, languages, operating systems and regions — the source of every valid targeting code.
RevContent Sub Accounts API
Create, edit, list and enable/disable child accounts under a parent account.
RevContent Targeting API
Per-campaign widget targeting and widget-level bid overrides.
RevContent Widget Internal Content API
Publisher-owned content injected into that publisher's own widget.
RevContent Widget Optimizer API
Campaign-level widget blacklisting.
RevContent Campaigns API
Create, update, list, archive and report on advertising campaigns (boosts).
RevContent Widget API
Publisher widget inventory, geo statistics and Sub ID reporting.
Scroll within the panel for all 12 ·
Open Collections 12
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONRevContent Access API
OPEN COLLECTIONRevContent Campaigns API
OPEN COLLECTIONRevContent CCPA API
OPEN COLLECTIONRevContent Content API
OPEN COLLECTIONRevContent Conversions API
OPEN COLLECTIONRevContent Helpers API
OPEN COLLECTIONRevContent Sub Accounts API
OPEN COLLECTIONRevContent Targeting API
OPEN COLLECTIONRevContent Widget Internal Content API
OPEN COLLECTIONRevContent Widget Optimizer API
OPEN COLLECTIONRevContent Widget API
OPEN COLLECTIONScroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Revcontent Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Revcontent Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Revcontent Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
RevContent API Rules
SPECTRALJSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessToken
JSON SCHEMACampaignCreateRequest
JSON SCHEMACampaignSettingsRequest
JSON SCHEMACampaign
JSON SCHEMACCPADataRequest
JSON SCHEMAContentItem
JSON SCHEMAConversion
JSON SCHEMAError
JSON SCHEMASubAccount
JSON SCHEMAWidgetTarget
JSON SCHEMAWidget
JSON SCHEMAScroll within the panel for all 11 ·
Examples 18
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Access Token Response
EXAMPLECampaign List Error Response
EXAMPLECampaign List Response
EXAMPLECampaign Settings Request
EXAMPLECcpa Data Request
EXAMPLECcpa Submit Request
EXAMPLEContent List Response
EXAMPLEConversion List Response
EXAMPLEHelpers Countries Response
EXAMPLEHelpers Devices Response
EXAMPLESub Account List Response
EXAMPLEWidget Blacklist Add Request
EXAMPLEWidget Blacklist Response
EXAMPLEWidget List Response
EXAMPLEWidget Subid Stats Response
EXAMPLEScroll within the panel for all 18 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for RevContent — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/revcontent · machine-readable index on apis.io
This is an independent, third-party profile of RevContent, 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.