OuterciteOutercite

API v1 reference

The public endpoints, their methods, authentication, pagination, errors and rate limits.

Base URL: https://app.outercite.com/api/v1. Authenticate with a bearer token. Every response is JSON.

What you'll learn

  • How to authenticate and what a response looks like
  • The endpoints, with their methods
  • Errors, pagination and rate limits

Authentication

curl -H "Authorization: Bearer $OUTERCITE_API_KEY" \
  https://app.outercite.com/api/v1/dashboard/stats

Keys are created in API settings and carry explicit permissions. A new key is read-only by default. See API access for the permission list.

Endpoints

Position and evidence

EndpointMethods
/dashboard/statsGET
/dashboard/intelligenceGET
/platforms/coverageGET
/citationsGET
/citations/{id}GET
/briefs/latestGET

Prompts

EndpointMethods
/keywordsGET, POST
/keywords/{id}GET, DELETE
/keywords/{id}/citationsGET
/keywords/{id}/trendsGET

The path says keywords and the product says prompts. They are the same object; the path is kept stable so existing integrations keep working.

Competitors

EndpointMethods
/competitorsGET, POST
/competitors/{id}GET, DELETE
/competitors/landscapeGET

The loop

EndpointMethods
/actionsGET
/actions/{id}PATCH
/recommendationsGET
/recommendations/{id}PATCH
/insightsGET
/insights/{id}/promotePOST
/audits/triggerPOST

Forecasts

EndpointMethods
/predictionsGET, POST
/predictions/{id}GET

Shopping

EndpointMethods
/productsGET, POST
/products/{id}GET, PATCH, DELETE

Trace

EndpointMethods
/citetrace/visitsGET

The ingest endpoints under /citetrace are used by the tag and the edge worker, not by your integration.

Keys and webhooks

EndpointMethods
/api-keysGET, POST
/api-keys/{id}DELETE
/webhooksGET, POST
/webhooks/{id}DELETE
/webhooks/{id}/testPOST

Common parameters

  • Pagination. List endpoints accept limit and offset, and return the total alongside the rows.
  • Filtering citations. platform, cited, tier and dateRange in days.
  • Agency scope. A key with the cross-workspace permission can scope a request to one client workspace.

Platform ids

chatgpt, claude, google_ai, google_aio, perplexity, grok, deepseek.

google_ai is Gemini. google_aio is AI Overviews. They are different surfaces, and an unrecognised id is rejected with the valid list rather than being quietly ignored.

Errors

Errors return a code and a message. The ones you will meet:

StatusMeaning
400Validation error. The message names the field and, where relevant, the valid values
401Missing or malformed Authorization header
403The key lacks the permission, or a plan limit blocks the action
404No such resource in this workspace
429Rate limited. The reset time is in the message and the limit headers

Rate limits

Your limit comes from your plan and is reported on the response headers, so a client can back off rather than guess. Use webhooks for event-shaped work instead of polling.

Try this in Outercite

Call GET /platforms/coverage with a read-only key. It confirms authentication, your covered surfaces and your rate limit headers in one request.

Was this helpful?

Last updated on