Overview - OAuth2 for apps
Build third-party OpenQuok apps that act on behalf of subscribed users using OAuth2 Authorization Code flow.
1 min read
Connect your agent today
Draft from chat, review in your calendar, and publish only what you approve.
Note
This section is for apps you register under Developers → Apps (client ID oqc_). For automation in your own workspace — scripts and CI — rotate a programmatic token under Developers → Access instead. See Public API authentication and CLI programmatic token.
Overview
OpenQuok supports OAuth2 Authorization Code flow, allowing you to build third-party applications that act on behalf of OpenQuok users.
Your app redirects users to OpenQuok where they approve access, and you receive an opo_ access token to call the public API on their behalf.
Implementation
Register your app, Authorization Code flow, API calls, and credential management
Node.js example
Copy-paste Express server with Authorization Code flow
Jev decision routing
Decide what to post (relevant, engaging, channel-fit), then create Global or per-channel OpenQuok drafts
Error reference
OAuth callback and token exchange error codes
Related configuration
Public API authentication
Workspace programmatic tokens (opo_) vs third-party OAuth
Admin: OAuth apps
Redirect URLs for hosted vs self-hosted servers and operator notes
Configuration - Backend
Backend env vars and public API surfaces