Register an app
Follow this guide to register an app in the Spoon Developer Center and get the Client ID and Client Secret you need for API integration.
What you need
- A Spoon account — apps are owned by the Spoon account you sign in with.
- A login redirect URL — the address of your service that users return to after signing in with Spoon.
The Spoon account that registers the app becomes the bot account. The bot chats and sends the listener notice under this account's name. If you register with a DJ's own account, the app can't be connected to that DJ's broadcasts — the consent screen ends with "This app can't be connected." Create a separate Spoon account for the bot and register the app with it.
Signing in to the Spoon app or web with the bot account is fine in itself. You can also do the follow a favorite manager needs right in the app. The Follow the DJ API does it too. Entering another broadcast in the app or on the web does not affect the bot either. The only problem is entering the same broadcast the bot is connected to with the same account. When that app or web session disconnects, the bot also leaves the room and the join message shows once more.
1. Open the Developer Center console
Sign in at the Spoon Developer Center and go to the console.
2. Register a new app
Click [Register app] in the console and fill in four fields.
| Field | Rules |
|---|---|
| App name | Up to 50 characters using Korean, Japanese, letters, numbers, and spaces. To avoid confusion with official services, names containing "spoon" (case-insensitive), "스푼", or "スプーン" are not allowed. Names must be unique, so the form checks for duplicates as you type. |
| Login redirect URL | Only https:// URLs are accepted. During development, http://localhost (with a port) is also allowed. |
| App purpose | Describe in up to 200 characters what your app does with the Spoon API. |
| API permissions (scopes) | Pick the permissions your app uses from the catalog. The catalog can change with review policy. |
Registering more than 5 apps fails with 429 (OAPI_CNSL_0005).
Delete an app you no longer use and try again.
3. Wait for review
A newly registered app is not usable right away — it enters review. Once it is approved, the app detail screen shows two credentials.
| Credential | Nature |
|---|---|
| Client ID | A unique, immutable identifier for your app. |
| Client Secret | A secret used only on your server. Click [Show] once the app is approved. |
While the app is pending or rejected, [Show] and [Regenerate] return 403 (OAPI_CNSL_0006).
A rejected app shows the reason on its detail screen. Edit and save it to send it back to review.
Anyone can extract a Client Secret embedded in browser code or a mobile app build. If you suspect a leak, click [Regenerate] on the app detail screen. The old secret is revoked immediately, and integrations using it stop working.
Next steps
Use your Client ID to get a DJ's consent. Once consent is
granted, exchange the code you receive for a token.