Skip to main content

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.

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.

FieldRules
App nameUp to 50 characters using Korean, 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 URLOnly https:// URLs are accepted. During development, http://localhost (with a port) is also allowed.
App purposeDescribe 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.
Up to 5 apps per account

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.

CredentialNature
Client IDA unique, immutable identifier for your app.
Client SecretA secret used only on your server. Click [Show] once the app is approved.
The Client Secret stays hidden until 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.

Keep the Client Secret on your server

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.