Portal Overview
The Developer Portal is where you create projects, build and submit your plugin, mint API keys, and test against a sandbox. This section is a screen-by-screen guide to using it.
If you have not registered yet, start with Developer Account — it covers registration, email verification, the developer agreements, and your first key. This page picks up once you can log in.
The screens
| Screen | What it is for |
|---|---|
| Dashboard | Your landing page: counts, quick actions, and your projects |
| Projects | Create projects and manage who can work on them |
| Project → Plugin | Build, edit, submit and publish the project's plugin |
| Sandbox | Run Plugin SDK calls and send signed test webhooks |
| My Plugins | Every plugin you have, across all your projects |
| API keys | Mint and revoke ssp_dev_ keys for CI |
| API reference | The Plugin SDK operations SSP currently publishes |
| Settings | Your account details, usage counts, and theme |
How your session works
Logging in gives the portal a session stored in an httpOnly cookie. The portal proxies GraphQL calls to the SSP backend on your behalf, so the browser never holds a bearer token.
Your dashboard session is only for the portal. It is not an ssp_dev_ key
and it is not a pik_ key. Programmatic and CI access needs a key you mint
yourself — see Keys and Account. The four credential
types and where each one is accepted are covered in
Authentication.
The dashboard
The dashboard is the first screen after login. It has four parts.
Your identity — name, company and email, with your initials as an avatar.
Three counts, which read 0 on a fresh account rather than sitting blank:
| Card | Counts |
|---|---|
| Projects | Projects across your account |
| Plugins | Plugins created from your projects |
| Active keys | ssp_dev_ keys that are neither deactivated nor revoked |
Quick actions — shortcuts to Projects, API Keys, API Docs and Sandbox.
My projects — a card per project. A brand-new account shows an empty state inviting you to create your first one, because a project is the container everything else hangs off.
Signing in again
Forgotten password
Request a reset from the Forgot your password? link on the login screen. SSP emails a link that expires shortly and can only be used once.
If clicking the link does not land you in the right place — some mail clients rewrite URLs — the reset screen accepts the full link pasted in, and pulls the token and email out of it. If you paste something that is missing either part, it tells you so rather than failing silently.
Verification email never arrived
The verification screen has a resend box: enter your address and SSP sends the link again.
Where to go next
- Projects and team — create a project and decide who can do what.
- Building your plugin — the six-step wizard, every field, and the review-to-publish path.
- Testing in the sandbox — the API Explorer and the Webhook Tester.
- Keys and account —
ssp_dev_keys, the API reference screen, and settings.
When you are ready to write code against the events, the Hello World tutorial in this section builds a receiver that handles every SSP event.