to navigate · to open See all results
DELETE /api/v1/subscriptions/{record}/todos/{todo}

Delete a subscription to-do

Delete a to-do belonging to this record.

Last updated

Request

DELETE /api/v1/subscriptions/{record}/todos/{todo}

Requires subscriptions:todos. See token permissions. Every listed permission is required for this endpoint.

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json. Send request bodies as JSON with Content-Type: application/json. This workflow write requires Idempotency-Key. Reuse the same key only when retrying the same action.

record is the numeric subscription ID in your token’s organization. todo is the numeric to-do ID belonging to this record; obtain it from the to-do list.

Request body

No body fields are required. Omit the request body.

Example

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization. Set IDEMPOTENCY_KEY to a new UUID for this action; keep it for retries.

cURL / Bash
curl --request DELETE "https://my.assetcenter.app/api/v1/subscriptions/123/todos/77" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY"

Response

200 OK. Illustrative response structure. Event arrays, to-do/space values, and current state depend on the action and the record.

JSON
{
  "data": {
    "subscription_id": 123,
    "subscription_event_ids": [],
    "todo": null,
    "state": {
      "status": "available",
      "billing_type": "subscription",
      "license_count": 10,
      "billing_frequency": "monthly",
      "price_model": "per_license",
      "cost": "12.00",
      "contract_term": null,
      "contract_start_date": null,
      "contract_end_date": null
    }
  }
}

Behavior and constraints

Returns a workflow result with todo: null.

Errors

401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 404 means the record or child record is unavailable in this organization. 409 indicates a conflicting state or concurrent change; inspect the message and refresh the record before deciding how to proceed. Reusing an idempotency key with a different method, path, or body also returns 409. 429 means a rate limit was reached. See error handling and rate limits.