Keys and Account
The remaining portal screens: API keys, the published API reference, the cross-project plugin list, and your account settings.
API keys
ssp_dev_ keys are for CI and programmatic access. Your dashboard session
does not need one, and a key is not a substitute for the pik_ key an
installation gets — see Authentication for which
credential belongs where.
Minting one
Give the key a name — required, and worth making descriptive, because the name is how you will tell keys apart when revoking one later. "Production integration" beats "key 2".
The full key appears immediately after creation and never again. Copy it into your secret store before dismissing the dialog. If you lose it, revoke it and mint another.
The cap
You may hold 10 active keys at a time. The screen shows your count against that cap, and disables minting when you reach it. Revoke something you are no longer using to free a slot.
What counts as active
A key is active when it has been neither deactivated nor revoked. The count on this screen and the "Active keys" figure on the dashboard use the same rule, so they cannot disagree.
Revoking
Revoking is immediate and permanent — the key stops working and cannot be restored. Mint a replacement first if something in CI depends on it.
Rotation practice and key hygiene are covered in Developer Account and Security.
API reference screen
Lists the Plugin SDK operations SSP publishes in the current contract, with request and response shapes per operation.
It reflects what SSP currently publishes, so it is the live answer rather than a snapshot. If it is empty, SSP has not published operations in the current contract — that is a real state, not an error. The narrative version of the same surface is API Reference.
My Plugins
Every plugin you have across every project, in one place. Plugins are always built inside a project, so this screen is for surveying, not creating — open one to manage it.
Two views:
- List — with filters by lifecycle state, each showing a count, so you can see at a glance what is in review versus live.
- Board — the same plugins grouped by state.
Settings
Account — your name, email, company, and your account ID. The account ID is the one worth knowing: it identifies you when contacting SSP support.
Usage — projects, plugins, and active API keys.
Appearance — theme.
Account management — account-level actions.
Where to go next
- Hello World tutorial — build a receiver for every event
- Plugin Data API — read and write restaurant data
- Plugin Lifecycle — review, pricing and publishing
- Security — hardening before you go live