Download for MacApple silicon, macOS 14+
Skill

inngest-api

@inngest Updated 2026-10-13

Use when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec, Bearer authentication with API keys or signing keys, production and local base URLs, raw curl/fetch requests, request-shape discovery, pagination, secret redaction, and when to prefer the `inngest-api-cli` skill instead.

Install

With your agent

Install OMGSkills skill "inngest/inngest-claude-code-plugin:skills/inngest-api" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/inngest/inngest-claude-code-plugin /tmp/inngest-claude-code-plugin && ln -s /tmp/inngest-claude-code-plugin/skills/inngest-api ~/.claude/skills/inngest-api

From README

Inngest REST API v2 For Cloud operations with connected MCP tools, use inngest-cloud first. Keep this skill for explicit terminal/HTTP work or a capability missing from MCP. Do not ask for an API key when OAuth MCP can complete the task. 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.