Build on your competitor intelligence.

Put Rival Ads inside reporting pipelines, internal dashboards and client workflows without rebuilding the monitoring engine behind them.

Open API reference Prefer an AI-native interface? Explore MCP

List competitor monitors

Rival Ads

curl https://www.rivalads.io/api/v1/monitors \
  -H "Authorization: Bearer ra_live_your_key"

One complete surface

From source setup to client delivery.

The useful automation seams are public, while billing rules, validation and tenant boundaries stay centrally owned.

Monitor operations: Create competitors across Meta, Google, TikTok and LinkedIn, change regions, move projects and request fresh syncs.
Structured intelligence: Read started, stopped and continuing creatives, exact evidence, sync health and stored strategic reads as predictable JSON.
Workflow building blocks: Manage client projects, shared swipe-file folders, saved ads and revocable public report links from one API.

Familiar by design

Plain HTTP. Predictable JSON. Useful errors.

Authenticate with a Bearer key, send JSON and follow cursor pagination. Validation failures point to the field; conflicts explain what must change.

Create a Google monitor

Rival Ads

curl -X POST https://www.rivalads.io/api/v1/monitors \
  -H "Authorization: Bearer ra_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "GOOGLE",
    "name": "Northstar",
    "googleDomain": "northstar.com",
    "regions": ["GB", "US"]
  }'

Production shape

No shadow implementation to drift.

Tenant-scoped by construction: Every key belongs to exactly one workspace. Resource IDs from another customer resolve as not found.
Safe, useful credentials: Choose read-only or read/write access, set an expiry and revoke instantly. Raw keys are shown once and stored hashed.
Async where the work is async: A sync request returns 202 with a job ID. Poll its state instead of holding a connection open through a source scrape.

Your first successful request is five minutes away.

Create a key in Developer settings, then use the live examples in the reference.

Read the API reference