Create developer portal with API explorer and playground

[Smartdevs17]

Description

Build a developer portal with interactive API documentation, GraphQL playground, and API key management.

Acceptance Criteria

• Swagger UI with interactive endpoint testing
• GraphQL playground for federated queries
• API key generation and management interface
• Usage statistics and rate limit status
• SDK download and quickstart guides
• Webhook testing tool

Technical Scope

• docs/
• api/src/routes/
• Edge: API key exposure in playground, CORS for playground requests

[Josetic224]

@Josetic224 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi Smartdevs17,

I’d like to claim this issue. I have experience building interactive developer tooling and integrating multi-protocol APIs (REST + GraphQL). I can ensure this portal is secure, intuitive, and production-grade.

My Implementation Plan:

Dual-Protocol API Documentation:

REST: I will set up an interactive Swagger/OpenAPI UI under /docs/api using swagger-ui-express (or the framework-equivalent route) that automatically parses our route decorators/JSDoc schemas.

GraphQL: I will deploy a production-hardened Apollo Sandbox or GraphiQL interface under /docs/graphql that handles federated schemas cleanly.

Secure API Key Management Interface: I’ll build the frontend UI components and backend routes for generating, rolling, and revoking API keys.

Security / Edge Mitigation: To address the API key exposure risk in the playground, I will implement a mechanism where keys are securely masked in the UI and stored in the browser's session storage only. I will also configure strict CORS profiles specifically for the playground domains (/docs/*) to prevent cross-site leaks.

Usage Telemetry & Rate-Limit Dashboards: I will build a lightweight dashboard component that fetches the developer’s current daily/hourly rate limit status and usage metrics (hitting our Redis/throttling middleware cache) so they can monitor their consumption in real-time.

Would you like me to draft the OpenAPI configuration block first to align on how we’ll structure the security definitions for API keys?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Josetic224 to this issue.

[Calebux]

@Calebux has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Calebux to this issue.

[drips-wave]

Congratulations, @Calebux! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Calebux: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊