Skip to main content

API Overview

The Zen Mesh API is one control surface for the Configuration Contract. It complements the UI, CLI, MCP, and Git surfaces. The contract — not any single surface — is the source of truth. See How Zen Works for the full mental model.

Status: PUBLIC_CONTRACT_DRAFT. This page describes the API surface groups and their current maturity. Individual endpoints may carry different statuses. See the API Status Matrix for per-group status.

API surface groups

GroupAudiencePrimary base pathStatus
Dashboard/BFF APIApp-facing/api/bff/v1INTERNAL_ONLY
Customer APIExternal programmable/v1/...PLANNED
Webhook Ingest APISender-facingPOST /webhooks/{provider}WIRED_SANDBOX
Targets APICustomer/v1/targetsWIRED_SANDBOX
Endpoints APICustomer/v1/endpointsWIRED_SANDBOX
Flows APICustomer/v1/flowsWIRED_SANDBOX
Delivery Attempts APICustomer/v1/delivery-attemptsWIRED_SANDBOX
DLQ APICustomer/v1/dlqWIRED_SANDBOX
Retry APICustomer/v1/retryWIRED_SANDBOX
Replay APICustomer/v1/replayWIRED_SANDBOX
Traces / Evidence Spine APICustomer/v1/tracesWIRED_SANDBOX
Saved Payloads APICustomer/v1/saved-payloadsWIRED_SANDBOX
Evidence APICustomer/v1/evidenceWIRED_SANDBOX
API Keys APICustomer/v1/api-keysWIRED_SANDBOX
Rate Limits APICustomerPUBLIC_CONTRACT_DRAFT
MCP APICustomerMCP protocolPUBLIC_CONTRACT_DRAFT
Billing/Plan APIInternalINTERNAL_ONLY
Sandbox/Test APITestSANDBOX_ONLY
Internal/Admin APIInternalINTERNAL_ONLY

Maturity legend

StatusMeaning
PUBLIC_CONTRACT_STABLEProduction-ready, documented, supported
PUBLIC_CONTRACT_DRAFTContract defined, API surface may change
WIRED_SANDBOXImplemented in local/sandbox runtime, not production-live
WIRED_LOCALImplemented in local development only
INTERNAL_ONLYApp-facing or admin dashboard, not a customer contract
SANDBOX_ONLYTest/sandbox endpoints, not for production use
PLANNEDDocumented intent, not implemented
V1_1_PLANNEDPlanned for V1.1 release
NOT_CLAIMEDExplicit non-claim — not available

Public-contract boundary

  • Some APIs are app-facing/internal (Dashboard/BFF routes).
  • Some APIs are public customer contracts (Customer API, runtime APIs).
  • Some APIs are sandbox-only (test event generation, sandbox delivery).
  • Some APIs are planned (Customer API GA contract).
  • No page should be interpreted as production-live unless the status field explicitly says PUBLIC_CONTRACT_STABLE.

Base URLs

Base URL examples in these docs use https://api.zen-mesh.io/v1 for public contract paths. Dashboard/BFF examples use /api/bff/v1 and are marked app-facing. Local/sandbox examples are explicitly labeled.

Terminology mapping

Customer termInternal API/model termAPI path
Targetdestination/destinations
Endpointingester/ingesters
Flowdelivery-flow/delivery-flows
Attemptdelivery/deliveries
DLQdeliveries?status=failed/deliveries?status=failed

Note: API paths use internal terms. Customer-facing documentation and UI use the customer terms. Where possible, OpenAPI field names and error messages prefer customer-facing language.

Customer chain

Template → Blueprint → Flow → Traffic → Evidence

Non-claims

  • API documentation is not proof of production availability.
  • Local/sandbox proof is not production-live proof.
  • Billing live is not claimed unless explicitly marked.
  • Provider live validation remains gated until public endpoint/provider proof exists.
  • Some endpoints documented here are app-facing only and not a public customer contract.