# token-invalid

The request to generate events carries a **token that SynthEvents does not accept**.

- **Status:** `401 Unauthorized`
- **Route:** `POST /api/v1/generate-events`
- **Description:** `token is invalid: expected a token issued for SynthEvents`
- **Details:** Empty. The response has the header **`WWW-Authenticate: Bearer`**.

## Why It Happens

The token after `Bearer` is not one that **the native web** issued for **SynthEvents**. Most often, it was not copied in full, or it picked up a line break or a space on the way. It may also have been changed, or have been issued for another product.

## How to Fix It

Copy the token again, in full, from the message you got it in, and send it in the header `Authorization`, after `Bearer` and a space. If SynthEvents still refuses it, ask for a new one with a **[tailor-made data set](/contact?topic=synthevents-tailor-made-data-set)**.