## 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:

```ts
const { userId } = await auth({ acceptsToken - 'api_key' })
```

2. Clerk's docs call this out for machine requests (API keys, OAuth tokens, machine tokens) hitting Route Handlers.

3. 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.
