An OAuth application gives your integration the client ID, and for a confidential application the client secret, that it needs to authenticate with our API. See Authentication for how to use them.
Note: You need the Admin permission for the account. Read more about permissions in Permissions.
Note: The client secret is shown only once. Only its hash is stored, so it cannot be shown again — rotate it if it is lost.
Choose Confidential for server-side applications that can securely store a client secret. Choose Public for browser, mobile or native applications that cannot — a public application gets no client secret, and PKCE protects the flow instead. The client type cannot be changed after the application has been created.
A redirect URI must use https, or http with a loopback address (localhost, 127.0.0.1 or ::1) for local development. A public application may also use a private-use URI scheme in reverse-domain notation, such as com.example.app:/oauth/callback.
Rotate the client secret if the current one has been lost or exposed. Only confidential applications have one.
The previous client secret stops working immediately, so update your application as soon as you rotate. Users who have already authorized your application stay authorized.
Deleting an OAuth application revokes the authorizations users have given it. Access tokens that have already been issued may keep working until they expire.