/Same route, personalized. The hero collapses into a compact welcome and the page leads with your recent specs and your sandbox activity. Both panels have an empty variant, shown below the populated one — a developer's very first sign-in has neither, and that state is contract, not an afterthought.
Signed in as dana.okafor@fuzefront.com · Developer on
FuzeFront Platform (root) · manage access
Resets in 6h 12m · quota is per developer, counted against
DevPortalPlayground:use.
Only your own calls
(DevPortalPlayground:view_history) — never another developer's.
/api/v1/apps
201
12m
/api/v1/apps/{slug}
200
14m
/api/v1/apps/{slug}
403
15m
A brand-new Developer has no history. The empty state must onboard, not just say
"nothing here".
Specs you open show up here so you can get back to them fast.
Browse the catalogOpen any endpoint and press Try it. Calls run against a mock generated from the spec — nothing you send here can reach production.
Open the PlaygroundSourced from .fuze/manifest.json → providesTo. A product appears here as
soon as one of its repos publishes a spec.
12 services · 8 specs
3 services · 3 specs
2 services · 2 specs
4 services · 4 specs
1 service · 1 spec
2 services · 2 specs
Test hooks: [data-frame='02-home-signed-in'] · [data-auth='authenticated'] ·
[data-membership-status='active'] · [data-panel='quota-summary'] ·
[data-panel='recent-specs'] · [data-panel='sandbox-activity'] ·
[data-panel='product-directory'] ·
[data-empty='no-recent-specs'] · [data-empty='no-sandbox-activity'].
Contract: GET /api/v1/devportal/me/activity, GET /api/v1/devportal/me/access.