Resolve Agent Workflow (M2M)
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 In: header
Path Parameters
uuidQuery Parameters
uuidResponse 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": {}}{ "detail": [ { "loc": [ "string" ], "msg": "string", "type": "string" } ]}