Introduction
The Storyblok Content Delivery API is organized around REST. It has predictable, resource-oriented URLs and uses HTTP response codes to indicate API errors. The API uses built-in HTTP features, such as HTTP query parameters and HTTP verbs, which are understood by off-the-shelf HTTP clients. Further, it supports cross-origin resource sharing, allowing you to interact securely with the API from a client-side web application (although you should never expose your secret API key in any public website's client-side code, the tokens configured in your Storyblok space are read-only therefore fine to use in client-side code). All API responses, including errors return JSON. Storyblok's API libraries convert responses to appropriate language-specific objects.
To make the API as explorable as possible, accounts have draft versions and published versions of API tokens. To access the draft version of your content, you can use the preview token, and for receiving published content, you can use the public token. The preview token also allows to load the published content. To switch between those versions, you can append the query parameter version=draft/published and use the appropriate token to perform a draft or published version request.
Region-specific base URLs
https://api.storyblok.com/v2/cdn