---
title: "Authentication"
description: "How customer keys work and which headers every request needs."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.withoutaworry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

Every request carries a customer key. One key belongs to one WaW customer team, and every record you create lands in that team.

## Headers

Send these headers with every request:

| Header | Value |
| --- | --- |
| `Authorization` | `Bearer <customer key>` |
| `Content-Type` | `application/json` |
| `Accept-Language` | Optional. `nl` returns Dutch error messages. English is the default. |

Requests must use HTTPS. Query strings are not accepted.

## Customer keys

- A key starts with `waw_partners_`.
- A key works in one environment only. An acceptance key returns `401` on production, and the other way round.
- Each customer team has its own key. You cannot use one customer's key to write to another customer's account.
- WaW can rotate a key. The old key stops working at once. Records you created keep their external IDs, so your mapping stays valid.

Keep keys in a secret store on your server. Never put a key in a browser, a mobile app, a URL or a log.

## When a key stops working

A valid key can still be refused. You get `403` when:

- WaW or the customer has revoked the connection.
- The customer's WaW subscription or trial is no longer active.
- The customer admin who approved the connection is no longer an active admin of the team.

Contact WaW when this happens. The customer may need to approve the connection again.

Source: https://docs.withoutaworry.com/partners-api/authentication/index.mdx
