Close an intervention

POST /api/v1/interventions/{interventionId}/close

Closes a planned intervention with the outcome it reached. The outcome is required for both results: cancelled without a reason would be indistinguishable from a deletion. The closure joins the member timeline and removes the intervention from the owner's work queue. A linked blocker stays open.

Authorization

Organization role

Business authorization

Closing does not require the enrollment to still be active: work that was started is finished, even after a suspension. Any caller allowed on the enrollment may close, not only the owner.

Path parameters

Request headers

Request body

{
  "result": "completed",
  "outcome": "Slot booked again on Thursday, the member resumed calling."
}

Example

curl -X POST "$COHORTE_API_BASE_URL/api/v1/interventions/INTERVENTION_ID/close" \
  -H "x-api-key: $COHORTE_API_KEY" \
  -H "Idempotency-Key: close-intervention-2026-09-04" \
  -H 'Content-Type: application/json' \
  -d '{"result":"completed","outcome":"Slot booked again on Thursday."}'

Response

• 200 OK — the intervention was closed.
• 400 Bad Request — missing Idempotency-Key, invalid JSON, an unknown result, or an empty outcome.
• 401 Unauthorized — the key is missing, invalid, or no longer attached to a member.
• 403 Forbidden — the bearer cannot act on this intervention's enrollment.
• 404 Not Found — the intervention is unknown or belongs to another organization.
• 409 Conflict — the intervention is already closed or cancelled.

Response fields

The rest of the object is the same shape as a planned intervention.

Example response

{
  "success": true,
  "data": {
    "id": "9f2c0a1e-0000-4000-8000-000000000000",
    "enrollmentId": "4af4cd8d-0000-4000-8000-000000000000",
    "reason": "late",
    "title": "Catch-up call after two weeks without progress",
    "channel": "call",
    "ownerUserId": "1b7d2f30-0000-4000-8000-000000000000",
    "ownerName": "Ines Fabre",
    "dueAt": "2026-09-05T16:00:00.000Z",
    "expectedOutcome": "A prospecting slot booked again for this week.",
    "status": "completed",
    "outcome": "Slot booked again on Thursday, the member resumed calling.",
    "closedAt": "2026-09-04T11:20:00.000Z",
    "closedBy": "1b7d2f30-0000-4000-8000-000000000000",
    "closedByName": "Ines Fabre",
    "blockerId": null,
    "plannedBy": "6d41ab55-0000-4000-8000-000000000000",
    "plannedByName": "Paul Vidal",
    "plannedAt": "2026-09-02T09:14:00.000Z"
  },
  "correlationId": "0f6b1d92-0000-4000-8000-000000000000"
}

Notes

• Closing is terminal and there is no reopening: a new follow-up is a new intervention.
• A second closing attempt answers 409, whether it comes from the same caller retrying or from someone else. Read the intervention first when a call timed out.
• The update, its audit entry and the intervention.closed event are written in one transaction.
• A completed intervention counts as a contact for the cohort cockpit; a cancelled one does not, and neither does a merely planned one.
• No email or notification is sent by this endpoint.

Related

• Plan an intervention
• List interventions
• Get the member timeline