Authentication

The Inngest API uses Bearer token authentication using your environment's signing key or an API key.

• Signing keys area an ideal method of authentication if you are making requests from an app or context that already has the signing key.
• API keys are ideal for making requests for all other contexts, like CI/CD pipelines, scripts, AI tools, or similar.

Keys

Signing key authentication

You can find your signing key in the Inngest dashboard under your environment's settings. The signing key begins with signkey- (learn more). When self-hosting Inngest, you'll have configured the signing key for your server via environment variable or configuration file.

Each environment has it's own signing key. Ensure that you are always using the correct key for the environment that you are managing.

API Key authentication (v2 endpoints only)

Inngest cloud allows organization admins to create and manage API keys within the Inngest dashboard. You can create one in the API key management panel.

Making Authenticated Requests

Include the api key or signing key as a Bearer token in the Authorization header of every request.

Authorization: Bearer signkey-prod-xxxxxxxxxxxxxxxxxxxx

Authorization: Bearer <api-key>

Examples

curl -X POST "https://api.inngest.com/v2/apps/demo-app/functions/backfill-data/invoke" \
  -H "Authorization: Bearer sk-inn-apixxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{ "data": { "test": "invoke-a-fn!" } }'

const appId = "demo-app";
const fnId = "backfill-data";
const response = await fetch(`https://api.inngest.com/v2/apps/${appId}/functions/${fnId}/invoke`, {
  method: "post"
  headers: {
    Authorization: `Bearer ${process.env.INNGEST_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ data: { test: "invoke-a-fn!" } }),
});
const data = await response.json();