Journey
OpenID Connect
We use industry standard OpenID Connect (OIDC) protocol to securely transfer user attributes to our customers.
Learn more about OIDC.
Sequence Diagram
The below sequence diagram shows the sequence of API calls, and user redirects.
sequenceDiagram
actor User
participant Your Service
participant OneID
Your Service ->> User: Redirect to OneID '/authorize?...' URL
User ->> OneID: GET /authorize?...
OneID ->> User:
Note over User,OneID: OneID will verify the user
OneID ->> User: Redirect to Your Service {redirect_uri}...
User ->> Your Service: GET {redirect_uri}?...
Your Service ->> OneID: POST /token
OneID ->> Your Service:
Your Service ->> OneID: GET /userinfo
OneID ->> Your Service:
Your Service ->> User:
Environments & APIs
We have two environments, sandbox and production.
The URLs for these, as well as our journey APIs, can be found in the Journey API ReferenceAPI.
Further Reading
- Create a Client - A step-by-step guide to creating an OAuth client.
- Verify a User - A step-by-step guide to verifying a user.
- Testing - A list of testing scenarios.
- Errors - A list of errors to handle.
- UX Guide - A guide to help you optimise your OneID service based on your use-case.
Was this page helpful?