Storyblok’s most used content delivery endpoint is trimmed for low latency and optimum availability.
To achieve low latencies all over the world, Storyblok uses a CDN in front of the API. The official Storyblok SDKs already take care of cache invalidation, so you don’t have to. But if you are doing the API calls on your own, you will need to append the
cv (cache version) parameter to the story API in order to get the latest version of the content. Have a look at Cache Invalidations for workflow descriptions.
You can load content entries from different spaces by using different access tokens for your requests. Your access tokens decide which space you want to access. With the query parameter
version you can switch between
published. Checkout Cache Invalidations if you want to know more about how you are able to invalidate the cache of your published content.