MCPBundler Docs
MCPBundler Docs
Back to marketplaceGetting StartedAuthenticationTutorial - Bundle to Connected Agent
API Reference
Agent A2A Tools
Agent Channels
Agent Configuration (Staging)
Agent Configuration (Versions)
Agent Tools
Agents
Auth
Billing
Bundler
Append Conversation Messages (M2M)Append Workflow Run Trace Step (M2M, fail-open)Create Conversation (M2M)Create Workflow Run (M2M)Dispatch a Matched Tool-Call Webhook (M2M)Finalize Workflow Run Outputs (M2M, fail-closed on the caller's side)Ingest Request TelemetryResolve An SMS Conversation Thread (M2M)Mint Widget Session Token (M2M)Reconcile Token LedgerReport An Outbound Call Outcome (M2M)Resolve Agent (M2M)Resolve Agent Config Snapshot (M2M)Resolve Agent for Inbound A2A (M2M, conditionally authenticated)Resolve BundleResolve Inbound Channel (M2M)Resolve LLM Credential (M2M)Resolve Telephony Credential For Outbound Origination (M2M)Resolve Tool-Call Override Bindings (M2M)Resolve Tool-Call Webhook Bindings (M2M)Resolve Public Widget Embed Key (M2M)Resolve Agent Workflow (M2M)Search Agent Knowledge Bases (M2M)Store Workflow Node Samples (M2M, fail-open)Submit Conversation Extraction (M2M)Update Conversation Status (M2M)Record Channel Status (M2M)
Bundler Tool
Bundles
Call Campaigns
Catalog
Conversations
Credentials
Deployments
Discover
Embedding
Fleet
Knowledge Bases
LLM
MCP Listings
Media
OAuth Clients
OAuth2
Observability
Organisations
Realtime
Reviews
Roadmap
SCIM
STT
Suppression
Triggers
TTS
Users
Utils
Voices
Webhooks
Workflows
API ReferenceBundler

Record Channel Status (M2M)

POST
/v1/bundler/channel-status

Record what agent-runtime observed when serving a call on this channel.

Deployment-scoped through the token that resolve_channel just minted, so one agent's runtime cannot write status onto another agent's channel. Without this the failure modes a caller hits - no balance, an unbound STT key - are invisible to the owner until somebody complains.

Should never be publicly reachable either - it is deployment-token gated rather than fully open, but that token is exactly what channel-resolve just handed out, so it carries the same "internal network only" placement requirement. See resolve_channel's own docstring and this module's own header docstring.

Authorization

BundleAccessToken
AuthorizationBearer <token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Body of POST /v1/bundler/channel-status.

Written by agent-runtime once a call completes or fails, so the channel's owner sees what happened without waiting for a complaint.

Response Body

application/json

curl -X POST "https://example.com/v1/bundler/channel-status" \  -H "Content-Type: application/json" \  -d '{    "channel_id": "bbe8aa76-a4bb-46f6-a785-df8e831cc459",    "status": "string"  }'
Empty
Empty
{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string"    }  ]}

Update Conversation Status (M2M)

Previous Page

Bundler Tool

Endpoints in the Bundler Tool group.

channel_id*Channel Id
Formatuuid
status*Status
Match^(active|error)$
status_detail?string|null