The Which AI Sent API: your AI leads and revenue, in your own tools

Since launch, the most common request from agencies has been some version of: “Can I get this data into the report I already send clients?” Marketing teams asked the same about Looker Studio and their internal dashboards. The dashboard is useful, but the number that matters, how many leads and how much revenue AI assistants sent, often needs to sit next to everything else. The API makes that possible.

What you can pull

Endpoint	What it returns
GET /api/v1/website	The website the key reads: name, addresses, how it's connected, whether tracking is on, and its plan
GET /api/v1/report?month=YYYY-MM	The monthly Overview report: visits by source (including each AI assistant), AI share of organic traffic, and leads and revenue from AI, broken down by assistant and by evidence level (Confirmed, Declared, Assisted), plus the rolling 90 days
GET /api/v1/leads?month=YYYY-MM	That month's leads, newest first (up to 1,000), each with its source, evidence level, status, booked value and revenue. Use range=30, 90, 365 or all for a rolling window.

Responses are JSON. The evidence labels come through exactly as in the dashboard, so a client report built on the API keeps the same honesty: tracked AI leads, customer-reported AI leads and assisted ones stay separate, and the AI figure remains a minimum you can defend. (Why that matters: Confirmed vs Declared, explained.)

Step 1: Create a key

1. In your dashboard, open Settings → API keys.
2. Give the key a name (for example “Looker Studio” or the client's name) and click Create API key.
3. Copy it straight away. It's shown once.

Each key reads one website, which suits agencies: one key per client, revoked in one click if a client leaves. Treat keys like passwords. Anyone with a key can read that site's leads, so keep them in a server or private script, never in a public web page.

Step 2: Make a request

Send the key as a Bearer token:

curl "https://whichaisent.com/api/v1/report?month=2026-09" \
  -H "Authorization: Bearer was_YOUR_KEY"

The limit is 120 requests per minute, which is far more than a daily report or dashboard refresh needs.

Example: AI leads in Google Sheets

In a Google Sheet, open Extensions → Apps Script, store the key as a script property named WAS_KEY, and add:

function aiLeads() {
  var r = UrlFetchApp.fetch('https://whichaisent.com/api/v1/leads?range=30', {
    headers: { Authorization: 'Bearer ' +
      PropertiesService.getScriptProperties().getProperty('WAS_KEY') }
  });
  return JSON.parse(r.getContentText()).leads;
}

From there you can write the rows into a sheet on a daily trigger, and point Looker Studio at that sheet for a client-ready AI leads report.

What agencies and teams are using it for

• Monthly client reports: add an “AI leads and revenue” section next to SEO and paid results, per client.
• Looker Studio dashboards: one AI line in the same place as every other channel.
• Internal scorecards: track AI's share of organic traffic and AI-sourced revenue month over month.
• Proving GEO work: show that AI visibility improvements turned into leads, not just mentions.

Reading data vs sending leads

The API reads data. If you want each new lead pushed into your CRM the moment it arrives, tagged with its AI source, use the built-in integrations (webhooks, Zapier, Make, HubSpot, GoHighLevel) instead. Many teams use both: the integration for real-time lead routing, the API for reporting.

Get started

Full reference, error codes and examples are in the API documentation. The API is included in Pro and Agency, and every Pro feature is free until October 31 as part of our launch offer, no card needed.