The shell shows the expected information architecture for apps, themes, API keys, analytics, and earnings. Each panel is tied to an existing endpoint or marked as a backend skip.
Live contract
Apps and submissions
Current developer apps and review records can be listed through `/v1/app-store/developers/apps` after a developer profile exists.
Developer registration is available at `/v1/app-store/developers/register`.
Partner dashboard aggregates are available at `/v1/app-store/partners/dashboard` for partner roles.
Marketplace app submissions are accepted at `/v1/app-store/developers/apps`.
Partial
Themes
Theme packages can be uploaded and reviewed, but a partner-owned theme dashboard endpoint distinct from marketplace operations is not present.
`POST /v1/themes/packages/upload` validates and persists JSON-contract bundles.
Self-serve theme listing metrics remain a planned partner API.
SKIP - NEEDS BACKEND
API keys
No partner API key inventory, create, revoke, or rotate endpoint is present in the gateway.
OAuth access tokens exist for app installs.
Embedded bridge tokens exist for installed embedded apps.
Long-lived partner key management needs a governed backend contract.
SKIP - NEEDS BACKEND
Analytics and earnings
Partner dashboard aggregates exist, but itemized app/theme earnings, payout exports, API call analytics, and install funnel analytics are not yet separate developer endpoints.
Render zero-state shell only.
Do not fabricate earnings, payouts, or API traffic.
Future data must come from `/v1/app-store/partners/dashboard` or a new partner API.