Open the generated endpoint reference for Expand APIs.
Exact endpoint contracts for Expand live in the generated API Reference. Open it for endpoints, request schemas, response schemas, errors, and rate limits.
The authored docs on this site explain concepts and tasks. The generated reference at /api-reference is the source of truth for request bodies, response fields, parameter tables, status codes, and generated code samples. When you open it, the left nav switches to the API Reference sidebar instead of mixing endpoint pages into the authored tree.
Each product page maps to a generated endpoint. Use this table to jump from a task to its exact contract.
| Authored page | Generated reference |
|---|---|
| Fetch Overview | fetch.fetch |
| Output Model | fetch.fetchJson |
| Include Options | and |
The /v1/fetch/search endpoint exposes Highlights. The product label is Highlights; the technical path keeps its search name.
Authored cURL examples authenticate with the x-expand-api-key header:
curl https://api.expand.ai/v1/fetch \
-H "x-expand-api-key: $EXPAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://news.ycombinator.com"}'SDKs read EXPAND_API_KEY from the environment by default. The generated reference may also document bearer and cookie auth, which the runtime supports; authored examples stick to the API-key header.
The API Reference area is available to agents and IDE tools as Markdown:
/api-reference.md/api-reference.mdx.md and .mdx routes for each endpoint pageAccept: text/markdown| Highlights | fetch.fetchSearch |
| Batched Fetch | fetch.batched and fetch.getBatched |