Secure by default
Use PKCE for public clients and keep client secrets on your server for confidential clients.
Let people sign in with Trek Point and call APIs on their behalf. Use the authorization code flow, PKCE for public clients, and standard token and revocation endpoints.
Start with the docs, then sign in to register an app and add redirect URIs.
Reference
Paths use your configured public base URL; /oauth
is the prefix shown here. For parameters, examples, and security guidance, see the
full docs.
Use PKCE for public clients and keep client secrets on your server for confidential clients.
Authorization code flow, token exchange, and revocation with familiar patterns for web and native apps.
Add redirect URIs in the developer portal and rotate client secrets when needed.
Sign in to continue