---
title: "Release a claimed event"
method: POST
path: "/v1/{account_id}/events/{event_id}/release"
tags: ["Webhooks"]
---

# Release a claimed event

`POST /v1/{account_id}/events/{event_id}/release`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/events/{event_id}/release`
- Auth: HTTP bearer

Hands a leased event back so it can be claimed again immediately. Use when your handler fails. Not checked against the original claimer: cooperative, not access control. Releasing an already-done event changes nothing.

## Path parameters

- `account_id` string, required
- `event_id` string, required

## Response `200`

The event's state after the release. A released event is claimable again immediately, by you or by anyone else. Releasing an event that is already done changes nothing and comes back with state done, because done is final. Release is the right move when your handler fails: hand the work back rather than sit on it for the rest of the lease.

- object
  - `object` 'event_lease', required: Response type discriminator.
  - `id` string, required: The event's id.
  - `state` 'unread' | 'claimed' | 'done', required: unread: claimable now. claimed: leased to someone until lease_until. done: handled, and it will never be handed out again. There is no failed state.
  - `claimed_by` string, nullable, required: The consumer name recorded by the last claim, or null. Free text, never verified, so treat it as a label rather than an identity.
  - `lease_until` string, date-time, nullable, required: When the current lease expires, or null when the event is not leased.
  - `done_at` string, date-time, nullable, required: When the event was marked done, or null. Set once and never moved.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `404`: No such event for this account, or it has already passed its 24 hour retention. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `429`: Rate limited, retry after the hinted delay.
- `500`: Internal error.
- `503`: Service unavailable.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)