Create a sandbox first. Mint a private key second.
Sign in to Developer Console, create a developer workspace and isolated test restaurant, then mint a server-side credential. Browser and native guest apps use public Storefront contracts; private keys stay in trusted server environments.
Three steps from account to test key.
Developer Console owns workspaces, sandboxes, keys, and the one-time reveal. A restaurant grants live access separately in Business Manager through an installation request.
- 01
Create an account
Sign up with Crave or use the developer identity you already have.
- 02
Create a developer workspace
Keep your apps, collaborators, and sandbox separate from every restaurant organization.
- 03
Provision a sandbox and key
Create an isolated test restaurant, name the server key, and copy its token once at creation time.
Keep the credential boundary visible.
The fastest route is only useful when the resulting credential lands in the right execution environment.
Server-side only
Use private keys from a trusted server process, never directly from a storefront or native client.
Shown once
Store the token securely when it is created. The dashboard does not reveal it again.
Public config is separate
The CLI can write public storefront settings without putting a private API key in the browser project.