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

Resolve Agent Workflow (M2M)

GET
/v1/bundler/workflow-config/{agent_id}

Resolve a WorkflowVersion for this agent, re-validating at resolve time.

Re-validation here is defense in depth against a definition made invalid outside the normal save path (direct DB write, a migration, a tool removed from the agent since the version was saved) - see the design spec's decision 9/12. This should never actually fail under normal operation, since save-time validation already covers the normal path; when it does, it is logged at ERROR (not a lower level) because its firing means something upstream is already broken, not that this is an ordinary declined call.

version_id is required and resolves a specific version for this agent - including a saved-but-not-live version (design spec's "Testing without touching production"), since there is no longer an "agent's own live workflow" fallback to resolve without it. 404s only when the agent itself is not found for this deployment, or when version_id does not identify a version belonging to this agent; every other precondition below - conversation_storage_enabled, resolve-time re-validation - still applies.

Authorization

BundleAccessToken
AuthorizationBearer <token>

In: header

Path Parameters

agent_id*Agent Id
Formatuuid

Query Parameters

version_id*Version Id
Formatuuid

Response Body

application/json

application/json

curl -X GET "https://example.com/v1/bundler/workflow-config/497f6eca-6276-4993-bfeb-53cbbbba6f08?version_id=497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "workflow_version_id": "60bab57e-9f59-448d-bef4-a6fd602db8a4",  "agent_config_version_id": "f0776ac6-b23a-4894-9ba1-e8f6f6f33247",  "definition": {},  "config_vars": {}}
Empty
Empty
{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string"    }  ]}

Resolve Public Widget Embed Key (M2M)

Previous Page

Search Agent Knowledge Bases (M2M)

Next Page