HTTP Binding
This page captures the MIG/HTTP binding reference from openapi/mig.v0.1.yaml.
Required Endpoints
Section titled “Required Endpoints”POST /mig/v0.1/helloPOST /mig/v0.1/discoverPOST /mig/v0.1/invoke/{capability}POST /mig/v0.1/publish/{topic}GET /mig/v0.1/subscribe/{topic}(SSE)POST /mig/v0.1/cancel/{message_id}POST /mig/v0.1/heartbeatGET /mig/v0.1/stream(WebSocket)
OpenAPI Definition (Excerpt)
Section titled “OpenAPI Definition (Excerpt)”openapi: 3.1.0info: title: MIG HTTP Binding version: "0.1.0"paths: /mig/v0.1/hello: post: operationId: hello /mig/v0.1/discover: post: operationId: discover /mig/v0.1/invoke/{capability}: post: operationId: invoke /mig/v0.1/publish/{topic}: post: operationId: publish /mig/v0.1/subscribe/{topic}: get: operationId: subscribe /mig/v0.1/cancel/{message_id}: post: operationId: cancel /mig/v0.1/heartbeat: post: operationId: heartbeat /mig/v0.1/stream: get: operationId: streamCanonical Header Schema
Section titled “Canonical Header Schema”MessageHeader: type: object required: [mig_version, message_id, timestamp, tenant_id] properties: mig_version: type: string message_id: type: string format: uuid timestamp: type: string format: date-time tenant_id: type: string session_id: type: string traceparent: type: string idempotency_key: type: string deadline_ms: type: integer minimum: 1For full operation semantics and error model, see Concepts and Core Specification.