BetaBuild · Guide
Build on advertised capabilities
Choose the current public contract for an integration and make the first scoped call without assuming every deployment is identical.
Make the first API callEstimated time5 minutes
Trust, applicability, and sourcesMobazha v0.3 release candidate
Integration rule
Use the connected backend's capability response and version information as runtime truth. Documentation describes interfaces and intent, but a client must handle unavailable, disabled, or differently versioned features.
Surfaces
- HTTP and WebSocket interfaces for commerce operations and live updates.
- Webhooks for operator-controlled event delivery.
- MCP and agent-oriented interfaces with explicit identity and authorization boundaries.
- Plugins and contracts only where the connected deployment advertises them.
Start building
Choose a surface and integration contract→Separate client shells, context routing, transports, events, and state authority.First authenticated API call→Discover capabilities and call a protected read.Authentication and scopes→Select Basic, hosted JWT, or scoped API token.Errors, retries, and idempotency→Preserve business correctness across unknown outcomes.HTTP API and OpenAPI→Use the generated operation and schema contract.Webhooks→Verify signatures, deduplicate, and reconcile.WebSocket→Treat events as refresh signals.MCP and agents→Initialize a scoped Streamable HTTP client.