Provider Conflict

provider-conflict · 409

Another provider on the platform already has this key, so nothing was written.

conflictField names the field and conflictValue the value it refused. Only operators reach the route that sends it.

Besides the members every error carries, this type adds resourceType, conflictField and conflictValue.

Common causes

  • Another provider on the platform already uses that key.
  • The same create was sent twice and the first one went through, so the second meets its result.

How to fix the call

  • Read conflictField and conflictValue: together they say which value was refused.
  • Pick another key, or fetch the provider that has it and use that one.
  • If the duplicate is your own retry, treat the call as done, not failed.
  • Send an Idempotency-Key header on writes, so a retry replays the first answer instead of colliding with it.

Example response

json
{
  "type": "provider-conflict",
  "title": "Provider Conflict",
  "detail": "A provider with key 'example-dc' already exists",
  "resourceType": "Provider",
  "conflictField": "key",
  "conflictValue": "example-dc",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/admin/providers",
  "method": "POST",
  "instance": "POST /v1/admin/providers",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/provider-conflict"
}