inngest-api

Inngest REST API v2 authentication uses a Bearer token in the Authorization header, typically an API key stored as INNGEST_API_KEY. For non-production Cloud environments, add the X-Inngest-Env header or use an environment-scoped API key.

Fetch the OpenAPI v2 spec at https://api-docs.inngest.com/api-specs/v2.json as the source of truth for methods, paths, parameters, and schemas. You can also append .md to any docs page URL or check the llms.txt index for markdown references.

Use the raw REST API only when the CLI does not expose the needed endpoint or when you explicitly need HTTP, curl, fetch, or OpenAPI details. The CLI is preferred for run debugging, account checks, and Insights workflows because it handles auth and target flags.

Yes, list responses include a page object with cursor, hasMore, and limit fields. Pass the cursor as a query parameter and keep fetching until hasMore is false to retrieve complete results.

The local dev server v2 API is available at http://localhost:8288/api/v2 and requires no authentication key. Confirm the actual dev server port before making local requests, and use https://api.inngest.com/v2 for Cloud.

Some operations like listing events, cancelling runs, bulk cancellations, and webhook updates still live in the v1 API at https://api.inngest.com/v1 with signing-key auth. Check the v1 docs before declaring an operation impossible.