Reference
Errors
Every Envie API error is a structured problem document with a stable type URL that resolves to a page here.
Every error the API returns is an RFC 9457 problem document — machine-readable, with a stable type URL you can open (or fetch) for the explanation and fix.
{
"type": "https://docs.getenvie.com/errors/plan-limit",
"title": "Plan limit reached",
"status": 403,
"detail": "The current plan allows 100 saved items. Upgrade to add more.",
"instance": "/v1/storefront/wishlist/toggle",
"requestId": "req-8fk2xj"
}typenever changes — branch on it, not ondetailwording.requestIdis what to quote to support.- Validation failures add an
errorsarray with per-field paths.
| Type | Status | Meaning |
|---|---|---|
| validation | 400 | Request shape or values invalid |
| unauthorized | 401 | Missing or unknown credentials |
| invalid-signature | 401 | App proxy signature rejected |
| forbidden | 403 | Auth mode can't do this |
| identify-forbidden | 403 | identify() from a browser |
| guest-disabled | 403 | Shop requires logged-in customers |
| share-disabled | 403 | Sharing turned off for the shop |
| plan-limit | 403 | Free-plan item cap reached |
| not-found | 404 | Resource doesn't exist |
| conflict | 409 | State changed under the request |
| rate-limited | 429 | Too many requests |
| internal | 500 | Our fault |