S256 and requires openid.
Register a client
Open your application at developers.boxpressd.com, then open OAuth.- Choose Public for browser or native clients that cannot keep a secret. Public clients must use PKCE.
- Choose Confidential only for a server application that can keep its client secret private.
- Add each exact redirect URL on its own line. HTTPS is required except for localhost development.
- Select
openidand the scopes your application needs. - Click Save OAuth settings and copy any newly issued secret immediately.
Supported scopes
Authorize the user
Generate a high-entropy PKCE verifier, deriveBASE64URL(SHA256(verifier)), and keep the verifier until the token exchange. Redirect the user to:
state before exchanging the code.
Exchange the code
client_secret. Public and native clients must not use one.
Access tokens are Bearer tokens valid for 15 minutes. Treat them as opaque. Authorization requests expire after 10 minutes, and one-time authorization codes expire after 2 minutes.
Current limitations
- Refresh tokens are not issued. Ask the user to sign in again after expiration.
- Persistent token revocation is not implemented.
/userinfoand consent-management endpoints are not implemented.- The public Developer API is read-only. User-authorized writes are coming soon.
https://oauth.boxpressd.io/.well-known/openid-configuration.