Skip to main content
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

Canonical string

  • 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 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