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

# Device signing

> Authenticate paired apps to /papi/* — algorithm summary and where the normative vectors live.

After pairing, every request except a fresh `POST /papi/pair` carries four headers and
an Ed25519 signature over a fixed canonical string.

Agents use RFC 9421. **Devices do not.** Keep the two schemes separate in your code.

## Headers

| Header | Value |
| - | - |
| `X-FAU-Device` | `device_id` from pair |
| `X-FAU-Timestamp` | Unix seconds |
| `X-FAU-Nonce` | Unique per request |
| `X-FAU-Signature` | base64url(Ed25519(canonical)) |

## Canonical string

```
fau/1 device
<METHOD>
<target including query>
<timestamp>
<nonce>
<sha256(body) hex>
```

* METHOD uppercased
* Empty body → SHA-256 of `""`
* Sign the exact bytes you transmit

## Normative vectors

Do not invent golden tests from memory. Reproduce:

**→ [Device signing vectors](https://docs.fau.run/developer/reference/device-signing.md)**

Those vectors are published on this site so you do not need a private checkout.

## Practical rules

* Keep clocks reasonable; nodes reject stale timestamps.
* Never reuse nonces.
* Do not pretty-print JSON after signing.
* Sign `/papi/activity?limit=50`, not `/papi/activity`, when that is what you send.

## Not the dashboard token

Mac UI uses loopback `X-FAU-Local`. Mobile apps **must not** obtain or send it. Your
surface is `/papi/*` only.

## Next

* [Phone API](https://docs.fau.run/developer/apps/phone-api.md)
* [App quickstart](https://docs.fau.run/developer/apps/quickstart.md)
* [Wire specification](https://docs.fau.run/developer/protocol/spec.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.