Spyglasses + Make

Send new placements into Spyglasses and pull your AI visibility metrics out with Make scenarios.

Make connects to Spyglasses through the REST API with the HTTP module. A scenario can post each new placement into a coverage group the day it runs, send a whole export in one call, and pull your metrics on a schedule into the sheets and reports your team uses.

Start free trial Read the automation guide

Jim Wrubel

Last updated October 2, 2026

Key takeaways

Inbound: the HTTP Make a request module posts placements to a coverage group.
Batch with an Array aggregator and send up to 1000 links in one call.
Outbound: a scheduled scenario pulls your metrics every day.
Coverage calls use your organization API key. Metrics calls use a property API key.
The API works on every Spyglasses plan.

HTTP · Make a requestCoverage ingest

URL              https://www.spyglasses.io/api/v1/coverage/groups/YOUR_GROUP_ID/items
Method           POST
Headers          x-api-key: YOUR_ORGANIZATION_API_KEY
Body type        Raw
Content type     JSON (application/json)
Request content  { "url": "{{1.link}}" }

What you can do

Scenarios teams build first.

Log new coverage automatically

Watch your coverage sheet, PR tracker or RSS feed, and post each new link to a coverage group. Spyglasses scores the placement and starts watching for AI citations.

HTTP · Make a requestPOST /api/v1/coverage/groups/:groupId/items

Send a weekly export in one call

Collect a week of links with an Array aggregator and send them as urls. Duplicates come back flagged, so overlapping exports are safe.

Array aggregatorHTTP · Make a request

Daily metrics and citations

Schedule the scenario to run every day, pull your latest metrics with a property key and new citations with the organization key, and add rows to a Google Sheet.

Scenario scheduleHTTP · Make a requestGET /api/v1/coverage/groups/:groupId/citations

Set it up in a few minutes

You need an organization API key, a coverage group, and an HTTP module.

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
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
Add an HTTP Make a request module
Set the method to POST, add the x-api-key header, choose a Raw JSON body, and map the link from your trigger into url. Turn on Parse response to read added and duplicates.
Coverage automation guide →
4
Optional: pull metrics on a scheduleOptional
In a second scenario, GET the metrics endpoint with a property API key and parse the response. The newest run is the first item.
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.

Run it on a schedule

Real-time scenarios fire per placement. Reporting scenarios run on the schedule you set.

Schedule metrics pulls daily, after the overnight tracking run.
Pass score: false when loading a large archive, and score it later in the app.
Log invalid from the response to catch a bad field mapping early.

The request content

Paste this into the module's Request content field and map your trigger's link into url.

{ "url": "{{1.link}}" }

Frequently asked questions

What to know before you connect Make.

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 Make'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 Make get new numbers from Spyglasses?

Make 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 build your first scenario in a few minutes.

Start free trial Read the automation guide

More integrations

All integrations →

ZapierAutomationLog new coverage automatically and pull metrics on a schedule.n8nAutomationBuild coverage and reporting workflows on your own n8n instance.Looker StudioReportingChart your daily metrics through the API and Google Sheets.ClaudeAI assistantsAsk Claude about your AI visibility and get client-ready reports.SemrushSEO and dataSemrush for SEO, Spyglasses for AI visibility, with Authority Score in AIPVS.