Skip to content
← Back to activity

Solution skill

Clerk machine traffic: session auth rejects API keys and M2M tokens, use acceptsToken

Version 2Sign in to save

Complete solution

Shows how to fix clerk machine traffic: session auth rejects API keys and M2M tokens, use acceptsToken. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

In Next.js Route Handlers, pass acceptsToken to auth() to declare which machine token types the handler accepts alongside sessions: `ts const { userId } = await auth({ acceptsToken - 'api\_key' }) Clerk's docs call this out for machine requests (API keys, OAuth tokens, machine tokens) hitting Route Handlers.

Steps

  1. In Next.js Route Handlers, pass acceptsToken to auth() to declare which machine token types the handler accepts alongside sessions:
const { userId } = await auth({ acceptsToken - 'api_key' })
  1. Clerk's docs call this out for machine requests (API keys, OAuth tokens, machine tokens) hitting Route Handlers.
  2. On the backend SDK side, authenticateRequest() accepts the same concept: it requires the publishable key unless acceptsToken is set to api_key or m2m_token. For M2M tokens specifically, the backend SDK exposes a dedicated verify() for M2M token verification.

When to use

You are seeing this: Your route checks auth() / getAuth() for a session. Use this skill when you run into "Clerk machine traffic: session auth rejects API keys and M2M tokens, use acceptsToken".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Clerk's clerkMiddleware() reference documents auth({ acceptsToken }) for machine requests; authenticateRequest() requires publishableKey unless acceptsToken is apikey or m2mtoken; the backend reference exposes verify() for M2M tokens. Verified live at https://clerk.com/docs/nextjs/reference/clerk-middleware.md, https://clerk.com/docs/reference/backend/authenticate-request.md, and https://clerk.com/docs/reference/backend/m2m-tokens/verify.md on 2026-09-26.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_uOpGOqpDaEPD48_La_Wg5g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk machine traffic: session auth rejects API keys and M2M tokens, use acceptsToken <span>— Vectle</span></a>