Offering Conflict

offering-conflict · 409

Another pricing offering in the catalogue already has this plan × region × provider × adapter, so nothing was written.

conflictField names the field and conflictValue the value it refused. Only operators reach the route that sends it. A provider left out shows as none.

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

Common causes

  • Another pricing offering in the catalogue already uses that plan × region × provider × adapter.
  • 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 plan × region × provider × adapter, or fetch the pricing offering 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": "offering-conflict",
  "title": "Offering Conflict",
  "detail": "A offering with plan × region × provider × adapter 'medium × amman-1 × none × ghaym' already exists",
  "resourceType": "Offering",
  "conflictField": "plan × region × provider × adapter",
  "conflictValue": "medium × amman-1 × none × ghaym",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/admin/pricing/offerings",
  "method": "POST",
  "instance": "POST /v1/admin/pricing/offerings",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/offering-conflict"
}