conflict

conflict

HTTP 409 Conflict
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/conflict",
  "title": "...",
  "status": 409,
  "detail": "...",
  "requestId": "req_01J..."
}

The change you asked for cannot be applied because of related records already stored for your account. The detail describes the conflict in plain words; it never contains database error text. This is different from idempotency-conflict, which is only about a reused Idempotency-Key.

Common causes

• Creating a record that already exists
• Deleting something another record still refers to
• A mapping override that would clash with an enabled override, has hit the per-account override limit, or no longer validates when you enable it

How to fix it

Read the detail, list the existing records (for example GET /v1/webhooks or GET /v1/overrides), resolve the clash, then retry. Retrying the same request unchanged returns the same error.

Does it bill?

No. See Test vs Live Keys for the full billing rules.

Related

• Mapping Overrides — limits and conflict checks
• Webhooks — managing endpoints
• Errors Overview — the problem+json shape and the closed catalog
• Every response carries an X-Request-Id; quote it when contacting support.