Skip to main content
An application is an OAuth 2.0 client. It is how a program reads and changes your account settings: workspaces, providers, models, keys, quotas, usage. This is a different credential from an API key. A key calls models through the gateway. An application calls the management API. Neither does the other’s job. Applications live in Settings, under Applications, not inside a workspace. They belong to your account and reach every workspace you have.

​
Creating one

You get back a client id starting cl_ and a client secret starting cls_. The secret is shown once. It is sealed after that and cannot be read back. If you lose it, regenerate it, which invalidates the old one immediately. Selecting authorization code adds refresh_token automatically, since a user facing app needs to refresh without sending the user back through consent.

​
Grant types

Client credentials is for your own backend acting as itself. No user is involved. See Client credentials. Authorization code is for acting on behalf of another nemu user, who approves the scopes on a consent screen. See Authorization code.

​
Scopes

Scopes are requested when the application is created and cannot be widened by the token request. Asking for more than the application holds fails. Grant the narrowest set that works. Full detail is in Scopes.

​
Managing them

Disable stops the application issuing new tokens without deleting it. Delete is permanent and revokes every token it ever issued. Authorized apps is the other side of the same page: applications, yours or someone else’s, that you have granted access to your own account. Revoking one there cuts its access immediately.

​
Next