Inngest REST API v2

Inngest REST API v2

Use this skill for raw REST API v2 work and API reference lookup. If the task can be completed through npx inngest-cli@latest api, use inngest-api-cli instead; the CLI is safer for agents because it handles target/auth flags and endpoint command wiring.

Prefer CLI First

Use inngest-api-cli for:

• Run and trace debugging from a run ID or event ID.
• Account, environment, key, webhook, app sync, and function invocation checks.
• Insights table/schema/query workflows.
• Local dev server or Cloud operational checks.

Use raw REST API v2 only when:

• The CLI does not expose the needed endpoint.
• The user explicitly asks for HTTP, curl, fetch, OpenAPI, or API docs.
• You need to inspect request/response schemas before deciding what to do.

Docs Lookup

When precision matters, fetch current docs instead of guessing:

• API overview: https://api-docs.inngest.com/
• Authentication: https://api-docs.inngest.com/authentication
• LLM index: https://api-docs.inngest.com/llms.txt
• OpenAPI v2 spec: https://api-docs.inngest.com/api-specs/v2.json
• Markdown page pattern: add .md to a docs URL, for example https://api-docs.inngest.com/v2/runs/GetFunctionTrace.md
• Endpoint request/response schemas: references/rest-api-v2.md

If a Markdown page returns an error or omits generated reference details, use the OpenAPI spec for methods, paths, parameters, request bodies, and schemas.

Base URLs