Google Shop Light Errors
Web DataShop Light uses the shared error shape with code, message, correlation_id, retryable, and details.
Error object
| Field | Type | Description |
|---|---|---|
code | string | Error code |
message | string | Human-readable message |
correlation_id | string | null | Keep this if you contact support |
retryable | boolean | Whether a retry may work |
details | object | null | Extra context |
A bad request body may return 422 with a detail list instead of code.
Status codes
| HTTP | What happened | What to do |
|---|---|---|
401 | UNAUTHORIZED | Check that X-Api-Key has a valid key |
402 | PAYMENT_REQUIRED | Check that your Google Shop Light plan is active and has requests left |
408 | TIMEOUT | The lookup ran out of time. Retry if retryable is true |
422 | Invalid parameters | Fix the field named in the response. Check the ID, the product link, and the more_stores range |
422 | PRODUCT_NOT_FOUND | Google has no product with that catalog ID. Check the ID or try another product URL |
422 | UPSTREAM_BLOCKED | Google declined the lookup. Retry the same request with backoff |
429 | RATE_LIMITED | Slow down and try again after a short wait |
500 | Internal server error | Check the details and retryable. Keep correlation_id |
502 | UPSTREAM_UNREACHABLE | Upstream could not be reached. Retry if retryable is true |
503 | SERVICE_UNAVAILABLE | The endpoint is temporarily down. Try again later |
Retry guidance
- Respect
retryable - Keep
correlation_idwhen you write to support
Billing reminders
- Failed lookups are free
- A returned product costs one request, even if the seller list is partial or completeness is unknown
Was this page helpful?