Workspace tools
The app workspace brings together release drafts, archive validation, publication preflight and scheduling, channels and audience access, listing edits, media and offer management. The security page holds automation credentials and publisher signing identities; Webhooks & license codes connects events and code batches.
Organization reports show sales and actual completed transfers. Release download counts measure completed distribution transfers, not installations, active users or running apps. The publisher export is paged and requires its reporting role and recent authentication.
API reference and tooling
The in-site API reference is generated from the same registered handlers and explicit policy as the private integration contract. It includes exact request/response schemas, supported credential kinds and revision requirements. Download its OpenAPI JSON for API tooling. Staff operations and development payment helpers are excluded from that site download.
Publisher automation credentials work only on routes with an explicit release scope. The private publisherctl utility can generate a signing key, sign a server challenge or release assertion, and verify incoming webhook bytes. Browser-only owner controls remain available through the site.
Documentation hosting
These guides live at /docs in the store so they are usable with the implementation today. Their content and generated reference can be reused at dev.praxical.io or praxical.dev once the owner selects the domain and configures hosting. The configured developer URL can point navigation at that destination without changing the API origin.
The repository and implementation source remain private. API documentation and purpose-written examples describe the integration surface; they do not publish the application repository. Current production, identity, payments, outbound email and independent desktop activation gates are tracked by the platform owner.