Competitor Tracker & Co. Docs

API reference

The Competitor Tracker & Co. REST API: base URL, authenticating with an OAuth token or API key, the shape of requests and responses, where every endpoint lives.

Everything Competitor Tracker & Co. does is here as a plain REST API over HTTPS. You subscribe to competitors, read the changes we caught, manage labels and dispatches, run your organization. JSON goes in, JSON comes out. Our lead detective C. T. Lucky checks every credential at the door. No badge, no entry.

Base URL

https://api.competitortracker.io/v1

Every route lives under /v1. The pages in this section give the full path for each one.

Authenticate

Every call to /v1/* needs a credential, and the API takes two kinds:

  • OAuth 2.0 bearer token for apps that sign a person in. Send it on the Authorization: Bearer … header. See Using OAuth2.
  • API key for scripts and headless jobs. Send it on the X-API-Key header. See Using API keys.

If both headers arrive the API key wins. What a credential may do comes down to its scopes and your role in the organization.

Requests and responses

Send and read application/json. List endpoints page with an opaque cursor: pass the nextCursor from one response as the cursor on the next. When something goes wrong the reply carries a machine-readable code and a human-readable message, so you can branch on the code and show the message.

When you need to slow down, that comes back the same way — a plain error telling you to back off.

Browse by area

Each area has its own page listing every endpoint, with a "try it" console on each call. The pages are generated from the live API description, so they track what the API actually serves.

New here? Getting started walks the whole flow end to end, from your first key to reading a competitor's changes. Prefer to drive it from an AI client? The same endpoints are exposed over the Model Context Protocol.

On this page