Agent Workflow

Promote Workflow

Changed on

Promote versions into a higher environment (DFCX, Bland).

Gated behind :func:require_promote_permission. On DFCX this deploys flow versions only (there is no deploy-playbook primitive); on Bland it publishes one pathway version to staging or production. Both providers record the deployment upstream; we log the Bluejay actor for audit.

post/v1/agents/{agent_id}/workflow/promote

Request

  • Base URL
    https://api.getbluejay.ai
  • URL
    https://api.getbluejay.ai/v1/agents/{agent_id}/workflow/promote
  • Auth
    HTTPBearer (a scheme the document does not define)

Path parameters

agent_idstring required

Headers

X-Organization-Idstring
X-API-Keystring required

API key required to authenticate requests.

Request body

environment_namestring required

DFCX environment resource name (…/environments/{id}), or 'production' / 'staging' for Bland

flow_version_namesstring[] required

Versions to deploy: DFCX flow version resource names, or one Bland version number

Response

Successful Response

object required

Changes