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 EntityADDRESS_INVALIDADDRESS_OUT_OF_RANGECART_EMPTYCATALOGSET_NOT_FOUNDCATALOGSET_REQUIREDCLIENT_CONTEXT_REQUIREDCLIENT_IP_INVALIDCLIENT_USER_AGENT_INVALIDITEM_UNAVAILABLEMODIFIER_REQUIREDORDER_ALREADY_PLACEDORDER_BELOW_MINIMUMORDER_TOTAL_DIFFERENTPRECISION_EXCEEDEDPAYMENT_DECLINEDPAYMENT_FAILEDPAYMENT_METHOD_INVALIDSESSION_USER_REQUIREDSTORE_CLOSEDSTORE_NOT_FOUND
powered by Zuplo
Errors

CLIENT_IP_INVALID

CLIENT_IP_INVALID

client.ip is not a usable public address for an end user.

Summary

FieldValue
HTTP status400
errorCategoryvalidation
retryablefalse

When This Fires

  • POST /v1/marketfront/orders/validate
  • POST /v1/marketfront/orders/place

…when client.ip does not parse as a single IP address, or parses but sits in a range no customer can originate from.

Rejected values

KindExamples
Private (RFC 1918)10.0.0.1, 172.16.0.5, 192.168.1.1
Loopback127.0.0.1, ::1
Unspecified / placeholder0.0.0.0, ::
Link-local169.254.10.1, fe80::1
Carrier-grade NAT (RFC 6598)100.64.0.1
Unique-local IPv6fd00::1
Reserved / documentation192.0.2.0/24, 198.18.0.0/15, 240.0.0.0/4
Not a single address203.0.113.7, 70.41.3.18, 203.0.113.7:8080, not-an-ip

An IPv4-mapped IPv6 address (::ffff:10.0.0.1) is evaluated as the IPv4 address it wraps, so it cannot be used to route around the list above.

Recommended Action

Two mistakes account for almost all of these:

  1. Sending your own server's address. Your backend's outbound address is usually private or a load-balancer address. Take the customer's address from the request your front end received.
  2. Sending the whole forwarded-for chain. client.ip is one address. If you have X-Forwarded-For: 203.0.113.7, 70.41.3.18, send the first entry — the client — not the joined string.
Code
{ "client": { "ip": "203.0.113.7", // one address, publicly routable "userAgent": "Mozilla/5.0 …" } }

We validate that the address is shaped like a real client address. We cannot verify that it belongs to the person ordering — that remains your responsibility under the integration agreement.

Example

Code
{ "type": "https://developer.gett-tech.com/errors/CLIENT_IP_INVALID", "title": "Bad Request", "status": 400, "detail": "client.ip must be the end user's publicly routable address. Private, loopback, link-local and reserved addresses are rejected — if your front end sits behind a proxy, forward the first address in the chain rather than your own server's.", "instance": "/v1/marketfront/orders/place", "requestId": "req_abc123", "timestamp": "2026-08-10T14:30:00.000Z", "errorCode": "CLIENT_IP_INVALID", "errorCategory": "validation", "retryable": false }
CLIENT_CONTEXT_REQUIREDCLIENT_USER_AGENT_INVALID
On this page
  • Summary
  • When This Fires
    • Rejected values
  • Recommended Action
  • Example
JSON
JSON