OpenAPI Spec

The Determ API is described by a machine-readable OpenAPI 3.1 document. Point an API client, a code generator, or an AI assistant at it instead of transcribing endpoints by hand.

Spec URL

https://developers.determ.com/openapi.json

Property	Value
Format	OpenAPI 3.1.0 (JSON)
Server	https://api.mediatoolkit.com
Auth	HTTP Bearer (bearerToken), applied to every operation

Import into an API client

Most API clients (Postman, Insomnia, Bruno) import OpenAPI documents. Choose the client's import from URL / link option and paste the spec URL — importing the URL rather than a downloaded file means you can re-import to pick up changes.

After importing, set the value for the bearerToken security scheme to your API token — the spec declares that a token is required but does not contain one. See Authentication for where to find it.

Generate a client

The spec has stable operationId values (getCurrentUser, createKeyword, scrollMentionsByKeyword, …), so generated method names stay put across regenerations.

TypeScript types

npx openapi-typescript https://developers.determ.com/openapi.json -o determ-api.d.ts

Any language

npx @openapitools/openapi-generator-cli generate \
  -i https://developers.determ.com/openapi.json \
  -g python \
  -o ./determ-python

Swap -g python for java, go, csharp or any other openapi-generator target — openapi-generator-cli list prints the full set.

Use it with AI tools

The spec is small enough to paste straight into a chat context window, and most coding agents can fetch it from the URL themselves. Two prompts that work well:

Read https://developers.determ.com/openapi.json and write a Python client
for scrollMentionsByKeyword that pages through every mention.

Using the attached OpenAPI spec, generate typed TypeScript request helpers
for the Determ mentions endpoints. Do not invent fields.

For conventions, gotchas, and worked examples, the AI Context File is the better input — the spec gives types, the context file gives judgement. See Develop with AI for more.

What's in it

• Every endpoint documented in the API Reference — and nothing else. Internal and admin endpoints are not published.
• Request and response schemas, with a response example on each success response.
• Error responses in the RFC 7807 problem format, wherever they apply. See Errors & Rate Limits.
• Per-operation rate limits as an x-rate-limit extension, plus the X-Rate-Limit-Remaining response header.

The spec is generated from these documentation pages together with the internal API schema, so it stays aligned with the API Reference. If you find a mismatch, treat the documentation page as authoritative and let Determ support know.