Actions
Create Actions
Changed onRecord work the customer decided to do themselves as actions, in the same shape as the ones Peec generates, so they sort, filter and move through the same statuses. The kind picked decides an action's type and group. The linked topic and prompts are resolved against the project, and an item naming one it does not hold lands in rejected on its own — the batch never fails as a whole.
post/actions/create
Request
- Base URLhttps://api.peec.ai/customer/v1
- URLhttps://api.peec.ai/customer/v1/actions/create
- 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": [
{
"topic_id": "to_a1b2c3",
"prompt_ids": [
"pr_a1b2c3"
],
"steps": [
{
"title": "Add a pricing comparison table",
"section": "Before publishing"
}
],
"due_on": "2026-10-31",
"title": "Add a pricing comparison table",
"completed_at": "2026-09-30T09:00:00Z",
"page_url": "https://example.com/pricing"
}
]
}Response
Per-item results, index naming the position in the request.
Changes
- info
endpoint added
- info