The Metrics API gives you the same aggregates the dashboard shows, as JSON, so you can blend them with GA4 or Search Console data in your own reports. Webhooks complement the API by pushing events from aeoora to your systems. API access is part of the Signal plan and higher.

Create an API key

  1. Open Settings, MCP and API Keys in aeoora Cloud.
  2. Click New key and give it a name.
  3. Copy the token, which starts with ans_. It is shown only once.

A key belongs to the person who created it and sees only brands that person’s workspace owns. Revoking it takes effect at once.

Make your first request

Send the key as a bearer token. whoami is a good connection test, and brands lists the brand IDs you need for everything else.

curl "https://app.aeoora.com/api/v1/brands" \
  -H "Authorization: Bearer ans_..."

Endpoints

All endpoints are GET, return JSON and live under https://app.aeoora.com/api/v1/.

  • brands and whoami: your brands, and who the key resolves to.
  • visibility-summary: score, mentions, citations and top competitors for a date range.
  • visibility-trend: day or week buckets, ready to join with GA4 dates.
  • competitor-comparison: head-to-head and share of voice.
  • citations, ai-traffic and prompt-performance.
  • shopping-cards: AI shopping results for your products.

Every metrics endpoint needs a brand_id. Most accept date_from and date_to as YYYY-MM-DD, plus filters such as model and region.

curl "https://app.aeoora.com/api/v1/visibility-trend?brand_id=BRAND_ID&granularity=day" \
  -H "Authorization: Bearer ans_..."

Errors return {"error": "..."} with 400 for bad parameters, 401 for a missing or invalid key and 404 for a brand outside your workspace. The Looker Studio connector is the no-code route to the same data.

Webhooks

Each brand has one webhook, configured under Content, Configure Webhook. Enter your endpoint URL, an optional secret and choose the events to receive. aeoora sends a JSON POST with an event field at the top level.

  • opportunity.sent: a content opportunity was sent to your workflow.
  • daily_pulse.created: a Daily Pulse was generated.
  • action_task.sent: an Action Center task was sent.
  • content_draft.sent: a Content Editor page was sent through the webhook. This one is opt-in.
  • webhook.test: sent when you press Test Webhook.

Verify requests

If you set a secret, every request carries it in an X-Webhook-Secret header. Compare it in constant time and reject mismatches. Use an https:// endpoint, since the secret travels in the request. Content draft events also include an HMAC-SHA256 signature of the raw body in an X-aeoora-Signature header, formatted as sha256= followed by the hex digest.

Next steps

Was this page helpful?

Tell us what was missing at support@aeoora.com, or contact the team.