Skip to content
ajar.Book a demo

Authentication

Dashboard sessions and provider connections.

Sign in to ajar

Sign in to ajar with an email link or a connected OAuth provider. NextAuth manages sessions in encrypted, HTTP-only cookies.

API credentials

Create API keys in Settings for account, workspace, and connector access. Choose read or read/write permission and the appropriate connector scope. Keep keys in your secret manager or local environment, never in client-side code or source control.

Provider connections

A dashboard session is separate from a provider connection. Starbucks and Rightmove use provider tokens that you store and send with each account request. Booking, Skyscanner, Depop, Amazon, Uber and Uber Eats use caller-held session tokens. Airbnb and Trainline guest reads use your ajar bearer token. Check the service’s connection guide.

Idempotency keys

Write operations that list x-idempotency-key require a unique identifier for one intended action. Generate a UUID with crypto.randomUUID(), or use 1–128 ASCII letters, numbers, hyphens, underscores or periods. Keep the identifier with your request record. Duplicate attempts are rejected, not replayed from a cached response. After a timeout or uncertain outcome, check the provider’s state before starting a new attempt; changing the key immediately can repeat an action that already succeeded. Read, quote and authentication operations do not require this header unless their reference says otherwise.

Session lifetime

Dashboard sessions expire after eight hours. Sign out from Settings to clear the session on this browser. Sign in again to start a new session.