Error Catalogportal-conflict

portal-conflict

409 Conflict — The dashboard action conflicts with the current state of your account.

portal-conflict

HTTP 409 Conflict
Content-Type: application/problem+json
{
  "type": "https://docs.transmute.403fin.io/errors/portal-conflict",
  "title": "...",
  "status": 409,
  "detail": "...",
  "requestId": "req_01J..."
}

The dashboard refused a change because of an account limit or because of something that already exists. The detail names the specific reason in plain words.

Common causes

  • The account has reached its API key limit
  • The one-time test allowance is spent, so new test keys cannot be created
  • Rotating a key that was already rotated or has expired, or rotating while too many live keys exist
  • Adding an IP block that is already on a key's allowlist, or adding to a full allowlist (20 blocks)
  • The account has reached its limit of connected accounting organisations
  • Claiming an email domain for single sign-on that another workspace already uses
  • A mapping override that clashes with an enabled override or no longer validates

How to fix it

Follow the detail: revoke an unused key, use a live key, rotate the newest key in the chain, remove an allowlist entry, or disconnect an organisation, then retry.

Does it bill?

Not applicable — portal routes are never metered. See Test vs Live Keys for the full billing rules.