Developer resources / Authentication
NAMA authentication guide.
NAMA workspace users sign in through the supported controls on the NAMA login page. The product supports password sign-in and email magic-link sign-in. Some workspaces may also show an identity-provider option configured by NAMA. Use only the choices displayed for your account; availability can vary by workspace and deployment.
For workspace users
- Use the official login page and the email address assigned to your workspace.
- A magic link is short-lived and intended only for the recipient who requested it.
- Do not forward a magic link, password, one-time code or session token.
- If sign-in fails, contact NAMA without including secrets or traveller documents.
For developers
NAMA does not currently issue public API keys, OAuth client credentials or personal access tokens. Private browser sessions and application endpoints are not a supported API authentication method. Do not copy cookies or automate the interactive login flow as an integration. A future public API will document its own credential lifecycle, scopes, rotation, revocation and error responses on this developer site.
Need an integration?
Describe the system, data flow and tenant scope you need. The NAMA team can confirm whether a supported route exists or record the requirement for the public platform.
hello@getnama.app