Gett Developer Portal
  • Welcome
  • Distribution Partners
  • Brand Partners
  • Commerce Partners
  • Ecosystem Partners
  • Errors
  • API Reference
Documentation
  • Get Started
  • Marketfront SDK
  • API Reference
Resources
  • Payments
Company
  • Gett
  • Terms of Service
  • Privacy Policy

Copyright 2026 Gett. All rights reserved.

409 Conflict403 Forbidden500 Internal Server Error400 Bad Request404 Not Found429 Too Many Requests503 Service Unavailable401 Unauthorized502 Bad Gateway422 Unprocessable EntityCATALOGSET_NOT_FOUNDCATALOGSET_REQUIREDCLIENT_CONTEXT_REQUIREDCLIENT_IP_INVALIDCLIENT_USER_AGENT_INVALIDITEM_UNAVAILABLEMODIFIER_REQUIREDORDER_TOTAL_DIFFERENTPRECISION_EXCEEDEDCARD_EXPIREDCARD_LOST_OR_STOLENINCORRECT_CVCINSUFFICIENT_FUNDSPAYMENT_DECLINEDPAYMENT_FAILEDPAYMENT_TOKEN_INVALIDPROCESSING_ERRORSESSION_USER_REQUIREDSTORE_CLOSEDSTORE_NOT_FOUND
powered by Zuplo
Errors

CONFLICT — 409 Conflict

409 Conflict

A conflicting operation has already occurred.

Category

conflict

Retryable?

Usually no. Resubmitting the same request will not help — most of these require either a changed request or a change in external state. Read retryable on the response rather than assuming: IDEMPOTENCY_KEY_IN_PROGRESS is the one 409 on this surface that carries retryable: true.

Common Error Codes

CodeDescriptionAction
CART_STALEThe store's menu changed since the cart was builtStart a new cart from the current menu
STORE_PAUSEDThe store is temporarily paused and not accepting ordersOffer another store, or retry after the pause lapses
ENVIRONMENT_MISMATCHThe store is not available for your account's environmentCheck whether you are using sandbox or live credentials
IDEMPOTENCY_KEY_IN_PROGRESSAn earlier request bearing this Idempotency-Key is still in flightRetry unchanged, on the same key, after the interval in the Retry-After header. Carries retryable: true and errorCategory: idempotency

Do not mint a fresh key for IDEMPOTENCY_KEY_IN_PROGRESS

This is the one error where reusing the key is the correct action. The in-flight attempt owns the outcome of your order — retrying the same key is how you learn what it was. A fresh key presents the same order to us as a new one, which is exactly how a duplicate order gets placed.

Error Codes

Each code below is an anchor. The type URI on a problem-detail response points straight at it, so dereferencing type lands on the exact code rather than the top of this page.

CART_STALE

The store's menu changed since the cart was built.

What to do: Start a new cart from the current menu.

STORE_PAUSED

The store is temporarily paused and not accepting orders.

What to do: Offer another store, or retry after the pause lapses.

ENVIRONMENT_MISMATCH

The store is not available for your account's environment.

What to do: Check whether you are using sandbox or live credentials.

IDEMPOTENCY_KEY_IN_PROGRESS

An earlier request bearing this Idempotency-Key is still in flight. This is the one 409 on this surface carrying retryable: true.

What to do: Retry unchanged, on the same key, after the interval in the Retry-After header. A fresh key here places a duplicate order.

Example

Code
{ "type": "https://developer.gett-tech.com/errors/CONFLICT#cart_stale", "title": "Bad request", "status": 409, "detail": "This store's menu changed since your cart was built, so the cart is no longer valid. Start a new cart from the current menu.", "instance": "/v1/marketfront/orders/place", "requestId": "req_abc123", "timestamp": "2026-03-11T14:30:00.000Z", "errorCode": "CART_STALE", "errorCategory": "conflict", "retryable": false }
403 Forbidden
On this page
  • Category
  • Retryable?
  • Common Error Codes
  • Error Codes
    • CART_STALE
    • STORE_PAUSED
    • ENVIRONMENT_MISMATCH
    • IDEMPOTENCY_KEY_IN_PROGRESS
  • Example
JSON