PEpeec
Actions

Update Action Status

Changed on

Move actions to a status by id: accept, reject, complete, delete, or send one back to PENDING. Ids the project publishes no action under are returned in skipped — the batch never fails as a whole. 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. Send completed_at with COMPLETED to record when the work was actually done.

post/actions/status

Request

  • Base URL
    https://api.peec.ai/customer/v1
  • URL
    https://api.peec.ai/customer/v1/actions/status
  • Auth
    • API key in header X-API-Key
    • or API key in query parameter api_key
    • or HTTP bearer

Request body

project_idstring

Required if using a company api key

action_idsstring[] required

Up to 50 action ids, from list_actions.

status'PENDING' | 'PLANNED' | 'ACCEPTED' | 'REJECTED' | 'COMPLETED' | 'DELETED' required
completed_atstring date-time

When the work was done, as an ISO 8601 date-time with an offset. Only a COMPLETED action takes one; it may be up to five years back and never in the future. Omitted means now. It is the date the action marks on the impact chart.

Example request

{
  "project_id": "or_f45b94ba-5e35-4982-93ed-285e72ee14eb",
  "action_ids": [
    "01a0422f-e0c4-7820-85a1-31515a321f15"
  ],
  "completed_at": "2026-09-30T09:00:00Z"
}

Response

Per-item status results

Changes