Integration · Automation

Spyglasses + Zapier

Send every new placement to Spyglasses the moment it lands, and pull your AI visibility metrics into the tools your team reads.

Zapier connects to Spyglasses through the REST API with Webhooks by Zapier. A Zap can post each new placement from your PR tracker, a sheet or an RSS feed into a coverage group, so AI citation tracking starts the day the story runs. Another Zap can pull your metrics every morning and drop them into a sheet or an email.

Jim Wrubel
Jim Wrubel

Last updated

Key takeaways
  • Inbound: a Webhooks by Zapier POST adds placements to a coverage group.
  • Outbound: a scheduled GET pulls your metrics into a sheet or an email.
  • Coverage calls use your organization API key. Metrics calls use a property API key.
  • Duplicates are free, so retries and overlapping triggers are safe.
  • The API works on every Spyglasses plan.
Webhooks by Zapier · POSTCoverage ingest
URL           https://www.spyglasses.io/api/v1/coverage/groups/YOUR_GROUP_ID/items
Payload Type  json
Data          url  →  (link from your trigger)
Headers       x-api-key     YOUR_ORGANIZATION_API_KEY
              Content-Type  application/json

What you can do

Zaps PR and agency teams build first.

01

Log new coverage automatically

When a new row lands in your coverage sheet or PR tracker, post the link to a coverage group. Spyglasses scores the placement and starts watching for AI citations.

Webhooks by Zapier · POSTPOST /api/v1/coverage/groups/:groupId/items

02

See which placements AI cites

Once a day, ask the citations endpoint for anything new since yesterday and log each hit, with the prompt and the platform, to a sheet your team reviews.

Schedule by ZapierGET /api/v1/coverage/groups/:groupId/citations

03

A morning metrics digest

Every morning, pull the latest share of voice, mentions and citations with a property key and add them to a Google Sheet row or an email to the account team.

Schedule by ZapierWebhooks by Zapier · GET

Set it up in a few minutes

You need an organization API key, a coverage group, and one Zap per job.

  1. 1

    Generate an organization API key

    Open Organization Settings, then API Key, and generate one. This is the key for anything under /api/v1, including coverage.

    Which key do I need? →
  2. 2

    Create a coverage group and copy its ID

    Create the group on the property in Spyglasses, then list the groups with the API to find its ID.

    curl "https://www.spyglasses.io/api/v1/coverage/groups?propertyId=YOUR_PROPERTY_ID" \ -H "x-api-key: YOUR_ORGANIZATION_API_KEY"
  3. 3

    Add a Webhooks by Zapier POST step

    Use your trigger's link field as the url value, and put the key in the Headers field, not the URL. Zapier logs request URLs in task history.

    Coverage automation guide →
  4. 4

    Optional: pull metrics on a scheduleOptional

    Add a second Zap with Schedule by Zapier and a Webhooks by Zapier GET to the metrics endpoint, using a property API key. The newest run is the first item in the response.

    https://www.spyglasses.io/api/properties/YOUR_PROPERTY_ID/historical-metrics/discovery
    Endpoint reference →

The REST API, organization keys and property keys are included on every Spyglasses plan. Admins and owners generate the organization key.

Batch it when volume grows

One placement per call is right for real-time triggers. For a weekly export from your PR platform, send the whole batch at once.

  • Send up to 1000 links in one call with urls instead of url.
  • Pass score: false when loading a large archive, and score it later in the app.
  • Check added, duplicates and invalid in the response to catch a bad field mapping.

The request body

This is what the POST step sends. Map the link from your trigger into url.

{ "url": "https://www.example.com/2026/09/acme-outdoor-review" }

Frequently asked questions

What to know before you connect Zapier.

Which API key do I use?

Use your organization API key for coverage, because one key covers every client property in the organization. Use a property API key to read one property's metrics. Both go in the x-api-key header, and you keep them in Zapier's credentials, never in the URL.

What if the same placement is sent twice?

Nothing breaks. Spyglasses matches URLs on a normalized form, so www, trailing slashes, UTM parameters and fragments all count as the same placement. A repeat comes back as a duplicate and costs nothing.

How does Zapier get new numbers from Spyglasses?

Zapier asks for them on the schedule you set. Daily prompt tracking runs once a day on ChatGPT, Gemini and Google AI Overviews, so a daily pull keeps every downstream sheet and report current.

How fast are new placements scored?

Scoring usually finishes within a minute of the call. Every active project that tracks the coverage group also re-checks its goals, so a placement AI was already citing gets credit for those earlier citations.

Which plans include the API?

Every plan. Admins and owners generate the organization key under Organization Settings, and any member with access to a property can copy its property key.

Track every placement from the day it runs

Start a free trial, create a coverage group, and connect your first Zap in a few minutes.

Spyglasses + Zapier: Automate Coverage and AI Visibility Data