POST
/
api
/
v1
/
actions
/
{action_id}
/
append_phase
curl --request POST \
  --url https://cloud.bytebeam.io/api/v1/actions/{action_id}/append_phase \
  --header 'Content-Type: application/json' \
  --header 'x-bytebeam-api-key: <api-key>' \
  --header 'x-bytebeam-tenant: <api-key>' \
  --data '{
  "name": "<string>",
  "trigger_on": {},
  "info": {}
}'
{
  "phases_triggered": [
    true
  ],
  "next_phase_index": 123,
  "end_timestamp": 123,
  "retry_on_failure_until": 123,
  "phases": [
    {
      "name": "<string>",
      "trigger_on": {},
      "info": {}
    }
  ],
  "status": "<string>",
  "id": 123,
  "release_notes": "<string>",
  "tenant_id": "<string>"
}

Authorizations

​
x-bytebeam-api-key
string
header
required

API key required to authenticate requests.

​
x-bytebeam-tenant
string
header
required

Tenant(Project) name required to identify the project.

Path Parameters

​
action_id
integer
required

Body

​
name
string
required
​
trigger_on
object
required
​
info
object
required

Response

200
application/json
​
phases_triggered
boolean[]
required
​
next_phase_index
integer
required
​
end_timestamp
integer
required
​
retry_on_failure_until
integer
required
​
phases
object[]
required
​
status
string
required
​
id
integer
required
​
tenant_id
string
required
​
release_notes
string
Called by dkron repeatedly for a scheduled action until it is finished. It retries failed actions if needed and updates schedule statusget schedule for an action