Skip to main content
After you’ve set up authentication and chosen the correct domain, these tips will help ensure smooth integration and optimal performance.
Experro automatically caches responses at the edge. If you suspect stale data:
  1. Check the CDN-Cache response header
    • HIT → Response served from cache
    • MISS → Response fetched fresh from the origin
  2. Force a cache purge
    In the Experro Admin Panel, navigate to Workspace Settings → Cache, and clear the relevant endpoint or entire cache.
For more on caching controls, see the Cache guide.
The old x-lang header has been removed. Instead, specify localization per request via the locale query parameter:
ParameterInDescription
localequeryLanguage or region code for response data.
The relevant details are available in the API Documentation for each endpoint wherever applicable
Many Delivery APIs offer both GET and POST variants for full‑text or filtered queries. Our recommendation:
  • Use GET whenever your query parameters stay under ~1 KB in total length.
  • Switch to POST if your query string (filters, facets, etc.) exceeds ~1 KB to avoid URL length limits in browsers or proxies.
• Verify no extra spaces or line breaks were copied.
• Check if the token has expired in the Admin Panel.
• Ensure you selected Full Access for write operations.
• For read‑only calls, confirm Read‑Only scope is sufficient.
• Tokens cannot be retrieved once created—delete the old one and generate a new token.
• Update all clients to use the new token immediately.
Still stuck? Reach out to Support with your tenant ID and a description of the issue, and we’ll be happy to assist.