https://docs.test.geena.eu/getting-started/index.html Getting Started Start here if you are integrating a client against the Geena User API for the first time. Authentication — email-OTP login, JWT session management, secondary-email verification. Partner OAuth Login — one-click login via a partner company’s OAuth2 IdP, session cookies, and how to onboard a new partner integration. GraphQL basics — the single unified endpoint, scope wrapping (user { ... }), error shape, nullable scope roots. Hugo en https://docs.test.geena.eu/getting-started/authentication/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/getting-started/authentication/index.html Authentication Geena uses email-OTP login backed by Ed25519-signed JWTs with server-side session revocation. No passwords, no third-party identity provider. Info If your users authenticate through a partner company’s identity provider (SSO-style), see Partner OAuth Login instead — it describes the one-click OAuth2 flow for partner-managed users. The OTP flow below is for users who log in directly to Geena with an email address. https://docs.test.geena.eu/getting-started/oauth-partners/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/getting-started/oauth-partners/index.html Partner OAuth Login In addition to email-OTP, Geena supports logging in via a partner OAuth2 identity provider. A partner company’s users click one link on the partner’s site, authenticate at the partner’s IdP, and land in Geena with an active session. Users don’t type a password on Geena, don’t pick a plan, and don’t see any registration form — everything is decided by the partner configuration we set up for you in advance. https://docs.test.geena.eu/getting-started/graphql-basics/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/getting-started/graphql-basics/index.html GraphQL basics One endpoint All GraphQL operations go to a single endpoint: POST https://api.test.geena.eu/graphql The server accepts POST, GET, and multipart form transports. For nearly everything you want POST with Content-Type: application/json. Scope wrapping The root schema exposes each API scope as a nullable field: