Register
- Open Apps in your account and press Register an app.
- Give the name people will see on the consent screen.
- Give the redirect URIs, one per line: where the authorization code is sent back. They have to use https, except on localhost.
- Tick 'I accept the Developer Agreement'. The link opens it: Developer Agreement. TAP records which version you accepted, when, and from which address.
The app starts in review. It can hold credentials, but reads nothing until we approve it. Approved, Denied and In review show on the list.
The profile
What people see when the app asks for access: an icon, a description, the website, and the terms and privacy policy. All of it shows on the consent screen. The name is part of the review; write to us to change it.
The credentials
The slug, the client ID, the redirect URIs, and the client secret. The slug is made from the name the way a handle is (lowercase letters and numbers, 3 to 30 characters) and never changes: it is the stable name integration settings know the app by. The secret is shown once, on the app's page right after you register it. Regenerating the secret replaces it at once; the app signs in with the new one or not at all. The secret is shown once.
Delete the app
Deleting takes the app and its credentials off TAP. Everyone signed in through it loses access at once, and the name is free for someone else to register.
What an approved app can do
Read artists and sign people in. Approval also lets the app's client get a token with client credentials, to read published artists with no person present: Quickstart. Writing to an artist needs a capability TAP grants the app on top of approval: Sign in with TAP: scopes and the consent screen. The partners page has the whole story: Partners.