Set Action Step Completion
Changed onRecord which of an action's steps are done. Each entry names one action and either sets completed for every step it holds, or lists the steps to write; a step in turn either sets completed for all of its options or names them individually, each with its own value, so one call can tick some and untick others. An action is all or nothing: anything Peec cannot apply leaves every step on it untouched and comes back under skipped or rejected, so a partly-written action is never a state you have to read back. Other actions in the same call are unaffected. The action's own status is never changed by this endpoint, including when every step on it is complete. An action that is already deleted reads as absent unless the key is a platform admin one. A content optimisation is reachable only on a project with content optimisation enabled; elsewhere its id is returned in skipped.
Request
- Base URLhttps://api.peec.ai/customer/v1
- URLhttps://api.peec.ai/customer/v1/actions/steps/completion
- Auth
- API key in header X-API-Key
- or API key in query parameter api_key
- or HTTP bearer
Request body
Example request
{
"project_id": "or_f45b94ba-5e35-4982-93ed-285e72ee14eb",
"actions": [
{
"action_id": "01a0422f-e0c4-7820-85a1-31515a321f15",
"steps": [
{
"step_id": "3f1c8a92-4d5b-4e77-9c21-8ab0f6d21e10",
"options": [
{
"option_id": "9d4e2b71-6c8a-4f13-b5d0-1e7a3c9f2b84"
}
]
}
]
}
]
}Response
Per-item completion results
Changes
- info
endpoint added
- info