OpenAPI-first
Endpoints are organized by product hierarchy so developers can find VoIP, Hosting, Monitoring, Cyber Security, and other modules consistently.
API Documentation
One contract for public clients, agents, and edge services.
MNSCloud is built around an API-first control plane. Public repositories consume the API contract, while authorization, tenant scope, billing, routing ownership, policy decisions, and secret resolution stay server-side.
Documentation surfaces
- Swagger UI/api/v1/docs
- OpenAPI YAML/api/v1/openapi.yaml
- Public repositoriesgithub.com/manaoscloud
- Contribution modelPull Requests, CI, and maintainer review
Integration Boundary
What public clients can rely on.
Public integrations should depend on documented API behavior, request/response examples, authentication requirements, and tenant-aware headers. They must not duplicate private control-plane decisions outside the API.
Safe examples
Public examples use placeholders and documented fields only. Secrets, customer data, production topology, and provider credentials stay out of public repositories.
Governed changes
API-facing changes are reviewed before merge. Public clients follow the API contract; the control plane remains the source of truth for authority and policy.
Next Step
Start the conversation Build integrations on the contract, not on private assumptions.
Talk to MNSCloud about deployments, integrations, public connectors, and enterprise security requirements.