Cathopic reviews a developer account once. That single approval unlocks both the commercial API and OAuth application management; you do not submit separate requests. After approval, you create and manage your API keys and OAuth credentials from Cathopic Settings. Developers never need a Cathopic server command or infrastructure access.
1. Prepare your Cathopic account
Create a Cathopic account, verify its email address, and make sure the username and email in the request match that account exactly.
2. Send the developer request
Open the Cathopic contact form.
Choose Request developer access.
Confirm the Cathopic username and describe the product, organization, and intended catalog use.
Send the form. The request appears in Cathopic's internal review dashboard.
3. Receive the decision
Cathopic reviews the account and use case. When approved, the developer receives an email with the next steps and a link to Settings → Developer / API → OAuth applications. If more information is needed, Cathopic contacts the email from the request.
4. Create the application
Choose a confidential web application when the product has a secure backend, or a public PKCE application for browser-only, mobile, or desktop clients. Enter its public name, description, website, privacy policy, security contact, exact callback URLs, and only the scopes it needs.
5. Store the credentials
The client ID identifies the integration and is shared by all of that product's users. User authorization and tokens remain separate for each Cathopic account. A confidential client secret is shown only once and must be encrypted on the application's server. Never include it in browser code, generated websites, logs, support messages, or a public repository.
The same page lets the approved developer edit callbacks and scopes, rotate a confidential secret, or revoke the application.
