Caching Behavior
Caching Behavior
Experro automatically caches responses at the edge. If you suspect stale data:
-
Check the
CDN-Cacheresponse headerHIT→ Response served from cacheMISS→ Response fetched fresh from the origin
-
Force a cache purge
In the Experro Admin Panel, navigate to Workspace Settings → Cache, and clear the relevant endpoint or entire cache.
Language Header Deprecation
Language Header Deprecation
The old
x-lang header has been removed. Instead, specify localization per request via the locale query parameter:The relevant details are available in the API Documentation for each endpoint wherever applicable
GET vs POST Endpoints
GET vs POST Endpoints
Many Delivery APIs offer both
GET and POST variants for full‑text or filtered queries. Our recommendation:- Use
GETwhenever your query parameters stay under ~1 KB in total length. - Switch to
POSTif your query string (filters, facets, etc.) exceeds ~1 KB to avoid URL length limits in browsers or proxies.
Token not recognized?
Token not recognized?
• Verify no extra spaces or line breaks were copied.
• Check if the token has expired in the Admin Panel.
• Check if the token has expired in the Admin Panel.
Permission denied?
Permission denied?
• Ensure you selected Full Access for write operations.
• For read‑only calls, confirm Read‑Only scope is sufficient.
• For read‑only calls, confirm Read‑Only scope is sufficient.
Lost your token?
Lost your token?
• Tokens cannot be retrieved once created—delete the old one and generate a new token.
• Update all clients to use the new token immediately.
• Update all clients to use the new token immediately.