RAMSESDeveloper Console
RAMSES.ID AUTHENTICATION

Let customers continue with Ramses.

Use standard OpenID Connect libraries. Ramses owns the QR, customer approval, consent and identity verification; your application owns its session and permissions.

Secure sign-in with Ramses.ID

How the flow works

1. Redirect

Your app starts Authorization Code with PKCE.

2. Approve

Ramses shows a QR on desktop or opens Ramses.Superapp on mobile.

3. Verify

Your backend exchanges the one-time code and creates its own session.

1. Get a client ID

Sign in to the Developer Console and prepare a separate registration for each test or production application:

  • Application name, website, logo and privacy-policy URL
  • Exact HTTPS callback URLs—wildcards are not accepted
  • Application type: server web app, SPA, iOS or Android
  • Requested scopes and a short reason for each

Keep production and test callback URLs separate, and register every callback exactly as your application will send it.

2. Start authorization

Generate a fresh state, nonce and PKCE verifier for every attempt, store them in your server session, then redirect the browser:

GET https://app.ramses.org/identity/oauth/authorize
  ?client_id=YOUR_CLIENT_ID
  &redirect_uri=https%3A%2F%2Fexample.com%2Fauth%2Framses%2Fcallback
  &response_type=code
  &scope=openid%20profile.basic
  &state=RANDOM_VALUE
  &nonce=RANDOM_VALUE
  &code_challenge=PKCE_CHALLENGE
  &code_challenge_method=S256

Never call the first-party /identity/browser-login/* endpoints. They are reserved for Ramses-operated portals and are not the third-party API.

3. Handle the callback

  1. Reject the response unless state exactly matches your stored value.
  2. Exchange the short-lived code from your backend using the original PKCE verifier.
  3. Verify issuer, audience, signature, expiry and nonce using Ramses discovery and JWKS.
  4. Create your own Secure, HttpOnly application session; do not put tokens in local storage.

Scopes and claims

ScopeYour app receivesStatus
openidPairwise stable user subRequired
profile.basicName and avatarCustomer consent
phoneVerified phone numberRestricted review

Continue in the Developer Console

Sign in with Ramses.ID to manage your applications, callback URLs, credentials and integration settings from one place.

Open Developer Console