Skip to main content
Use Boxpressd OAuth when your application needs data that belongs to a Boxpressd user. The flow uses OAuth 2.0 Authorization Code with PKCE S256 and requires openid.

Register a client

Open your application at developers.boxpressd.com, then open OAuth.
  1. Choose Public for browser or native clients that cannot keep a secret. Public clients must use PKCE.
  2. Choose Confidential only for a server application that can keep its client secret private.
  3. Add each exact redirect URL on its own line. HTTPS is required except for localhost development.
  4. Select openid and the scopes your application needs.
  5. Click Save OAuth settings and copy any newly issued secret immediately.

Supported scopes

Authorize the user

Generate a high-entropy PKCE verifier, derive BASE64URL(SHA256(verifier)), and keep the verifier until the token exchange. Redirect the user to:
Validate the returned state before exchanging the code.

Exchange the code

Confidential clients also send 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.
  • /userinfo and consent-management endpoints are not implemented.
  • The public Developer API is read-only. User-authorized writes are coming soon.
Discovery metadata is available at https://oauth.boxpressd.io/.well-known/openid-configuration.