conflict

HTTP status: 409

The resource is in a state that makes the requested operation impossible.

Why this happens

• Attempting to activate a license that is already active.
• Attempting to close an account that has active subscriptions.
• Attempting to create a resource that already exists with the same unique identifier.
• A concurrent request completed the same state transition before this one arrived.

What to do

1. Fetch the current state of the resource with a GET call and inspect its status field.
2. Determine whether the desired end state is already achieved — if so, the operation was a no-op and no retry is needed.
3. If the state is genuinely incompatible (e.g., a subscription must be cancelled before closing the account), complete the prerequisite operation first.
4. If the conflict was caused by a race condition, retry with a brief back-off.

Example response

{
  "type": "https://zyins.isaapi.com/errors/conflict",
  "title": "Resource conflict",
  "status": 409,
  "detail": "License 'lic_01HZK2N5GQR9T8X4B6FJW3Y1AS' is already in status 'active'. No change was made.",
  "code": "conflict",
  "advice_code": "fetch_current_state",
  "param": null,
  "request_id": "req_01HZK2N5GQR9T8X4B6FJW3Y1AS"
}

SDK exceptions

See also

• Error catalog
• idempotency_conflict — returned when an idempotent endpoint receives the same key with a different body
• Idempotency guide — how the 24-hour replay window and the dedupe key work