Overview - OAuth2 for apps
Build third-party OpenQuok apps that act on behalf of subscribed users using OAuth2 Authorization Code flow.
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 uses OAuth2 Authorization Code flow for third-party apps. You register an app in the dashboard. Users approve access on OpenQuok. Your server exchanges the code for an opo_ token and calls /api/v1/public/* for that workspace.
How it works
The user picks one workspace on the consent screen. The token applies only to that organizationId. Exchange the code on your server with your oqs_ client secret. Do not put the secret in a browser or mobile app.
Tip
Step-by-step parameters, callback query strings, and curl examples are on Implementation. A runnable Express sample is on Node.js example.