Outcome
Release an unused reservation so it stops counting toward the contact's caps. Releasing a reservation that is already released or consumed changes nothing. A remote reservation taken through a connector is released there too (remote[]).
Before you start
- Verify identity and pin the intended organization and environment before discovering the action.
- Discover a granted Nurture workspace. The application permission is workspace:write; required workspace access is read_write. A permission alone does not supply a workspace grant.
- Organization and workspace come from verified context. Select resourceType/resourceId separately from action input; body fields cannot grant a different organization or workspace. The first authorized product action can initialize an identity-only workspace mirror.
- Obtain authorization for the documented effect or personal-data export before supplying CLI --confirm or MCP confirm:true.
Discover the target
topolo whoami --json
topolo actions get app_topolo_nurture.eligibility.reservations.release --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
id: Reservation id returned by an allowed eligibility.reserve outcome; a denied outcome has no reservation.
Request
POST /api/eligibility/reservations/{id}/release
Save action input as payload.json. The reviewed plan separates path identifiers, query fields and HTTP body. Set NURTURE_WORKSPACE_ID from granted resource discovery; it is separate from action input.
Inspect and test this action in the signed action console. A test response still requires the verification below.
Input fields
| Field | Required | Type | Constraints |
|---|---|---|---|
id | Required | string | Reservation id returned by an allowed eligibility.reserve outcome; a denied outcome has no reservation. {"minLength":1,"maxLength":64} |
reason | Required | string | {"minLength":1,"maxLength":200} |
Exact input schema:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 64
},
"reason": {
"type": "string",
"minLength": 1,
"maxLength": 200
}
},
"required": [
"id",
"reason"
],
"additionalProperties": false
}
Effects
- Marks a reserved send as released with the given reason, then releases each remote reservation it took through a connector; remote[].released false means that remote release failed and the remote slot expires on its own.
Interpret the response
The returned identifier path is $.id for send_reservation. Empty lists do not discover a target.
Call app_topolo_nurture.eligibility.check for the contact and confirm the cap no longer counts the released send.
Exact success schema:
{
"type": "object",
"required": [
"released",
"id",
"remote"
],
"properties": {
"released": {
"type": "boolean"
},
"id": {
"type": "string"
},
"remote": {
"type": "array",
"items": {
"type": "object",
"required": [
"connectorId",
"released"
],
"properties": {
"connectorId": {
"type": "string"
},
"released": {
"type": "boolean"
}
}
}
}
}
}
Worked examples
Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Replace synthetic identifiers using credential-scoped discovery. A local success is not evidence of a deployed effect, configured provider or delivered message.
Successful request
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "rsv_6028566ba33343d3b7a40cb85ce0cc8a",
"reason": "x"
}
CLI:
topolo actions validate app_topolo_nurture.eligibility.reservations.release --data @payload.json --json
topolo actions plan app_topolo_nurture.eligibility.reservations.release --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.eligibility.reservations.release --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_nurture.eligibility.reservations.release",
"input": {
"id": "rsv_6028566ba33343d3b7a40cb85ce0cc8a",
"reason": "x"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"released": true,
"id": "rsv_6028566ba33343d3b7a40cb85ce0cc8a",
"remote": [
{
"connectorId": "con_fa980ba926c149fa8ad7d6e7b5451b45",
"released": false
}
]
}
HTTP 200. Call app_topolo_nurture.eligibility.check for the contact and confirm the cap no longer counts the released send.
Another supported request
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "rsv_b8adc466a50d44cd8301244a6755c442",
"reason": "x"
}
CLI:
topolo actions validate app_topolo_nurture.eligibility.reservations.release --data @payload.json --json
topolo actions plan app_topolo_nurture.eligibility.reservations.release --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.eligibility.reservations.release --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json
MCP tool and arguments:
{
"tool": "topolo_call_action",
"arguments": {
"actionId": "app_topolo_nurture.eligibility.reservations.release",
"input": {
"id": "rsv_b8adc466a50d44cd8301244a6755c442",
"reason": "x"
},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>",
"confirm": true
}
}
Captured local response · HTTP 200:
{
"released": true,
"id": "rsv_b8adc466a50d44cd8301244a6755c442",
"remote": [
{
"connectorId": "con_fa980ba926c149fa8ad7d6e7b5451b45",
"released": false
}
]
}
HTTP 200. Call app_topolo_nurture.eligibility.check for the contact and confirm the cap no longer counts the released send.
Refused request · reservation_not_found
Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.
Input · payload.json:
{
"id": "rsv_1cab4bb154f24b5399eb075e1d9dca84",
"reason": "x"
}
CLI:
topolo actions validate app_topolo_nurture.eligibility.reservations.release --data @payload.json --json
topolo actions plan app_topolo_nurture.eligibility.reservations.release --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
Captured local response · HTTP 404:
{
"error": {
"code": "reservation_not_found",
"message": "No reservation with this id exists in this workspace."
}
}
HTTP 404. Preserve the refusal details and do not claim success.
Verify the result
- Call app_topolo_nurture.eligibility.check for the contact and confirm the cap no longer counts the released send.
Errors and recovery
organization_required(HTTP 403): Select an organization available to the verified caller before choosing a Nurture workspace.permission_denied(HTTP 403): Grant the credential the required Nurture workspace permission.workspace_required(HTTP 409): Create a Nurture workspace, or pass the workspace resource context.invalid_input(HTTP 422): Correct the fields named in error.details using inputSchema, then retry.reservation_not_found(HTTP 404): Use a reservation id returned by eligibility.reserve in this workspace.
Auth or gateway failures may precede this handler. Preserve the exact response shape, error string/code, request id and credential context; no synthetic fixture establishes live credential access.
Recovery boundary
A released reservation cannot be restored; reserve again with a new idempotencyKey.
Related actions
- Reserve a send slot: Check eligibility for one contact and, when eligible, atomically reserve a send slot that counts toward the caps for 15 minutes (or until released). Idempotent by idempotencyKey: a repeat returns the same live reservation without re-counting caps, or granted false with reservation_expired once released or expired. Applies the same suppression, subscription and pacing rules as app_topolo_nurture.eligibility.check; transactional messages need messageCategory. For marketing and outreach a granted reservation includes listUnsubscribe: a signed one-click unsubscribe URL and POST body for the message body. Nexus owns the List-Unsubscribe headers; pass the preference centre to email.send as unsubscribe_landing_url. With an active suppression_sync connector, a connector-sourced contact is also reserved in that system (TopoloCRM eligibility.reserve) and the stricter answer wins: a remote refusal releases the Nurture reservation and returns its reasons. Sends nothing.
Evidence
Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Test scenario and capture digests are retained with each fixture.