Authentication styles
How Asembla proves itself to a node.
Updated 2026-10-15
| Style | What is sent |
|---|---|
| Bearer | Authorization: Bearer <key> |
| Custom header | Any header name and value, for example X-Asembla-Key. |
| Username / password | Basic authentication. |
| OAuth / Supabase | A token from the node's sign-in service. |
| None | Public endpoints only. |
Header names and values are stored encrypted. Personal account keys for travellers are separate — see Sign-up and sign-in doors.
Was this helpful? No — ask support
Still stuck? Ask support.