How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Storyblok Stories API

Stories are the content entries in Storyblok. Each story is defined by a component schema and holds the content of a page, post, or any other structured content type.

Storyblok Stories API is one of 11 APIs that Storyblok publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Stories. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 10 operations across 7 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 6 base URLs: https://api.storyblok.com/v2/cdn, https://api-us.storyblok.com/v2/cdn, https://api-ap.storyblok.com/v2/cdn, https://api-ca.storyblok.com/v2/cdn, https://api-cn.storyblok.com/v2/cdn, https://mapi.storyblok.com/v1.

10 operations 7 paths 6 schemas 1 DELETE7 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.storyblok.com/v2/cdn
Authentication
API Key, HTTP Bearer, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 3

Storyblok Stories API declares 3 security schemes for authenticating requests. An API key is passed in the query as token (apiToken). It accepts HTTP bearer tokens (personalAccessToken). It accepts HTTP bearer tokens (oauthToken).

  • apiToken — Public API token for accessing published content, or Preview API token for accessing draft and published content. Tokens are scoped to a specific Storyblok spa…
  • personalAccessToken — Personal access token generated in the Storyblok account settings. Provides access to all spaces the account has permissions for.
  • oauthToken — OAuth 2.0 access token for third-party application integrations. Scoped to specific spaces and permissions granted during authorization.

Paths & Operations 10

Across 7 paths, the API surfaces 10 operations — 1 DELETE, 7 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Stories 10

Stories are the content entries in Storyblok. Each story is defined by a component schema and holds the content of a page, post, or any other structured content type.

GET
/stories
List multiple stories
listStories 20 params → 200401422
GET
/stories/{slug}
Retrieve a single story by slug
getStoryBySlug 7 params → 200401404
GET
/stories/{id}
Retrieve a single story by ID
getStoryById 5 params → 200401404
GET
/spaces/{space_id}/stories
List stories in a space
listManagementStories 12 params → 200401
POST
/spaces/{space_id}/stories
Create a story
createStory 1 param body → 201401422
GET
/spaces/{space_id}/stories/{story_id}
Retrieve a single story
getManagementStory 2 params → 200401404
PUT
/spaces/{space_id}/stories/{story_id}
Update a story
updateStory 2 params body → 200401404422
DELETE
/spaces/{space_id}/stories/{story_id}
Delete a story
deleteStory 2 params → 200401404
GET
/spaces/{space_id}/stories/{story_id}/publish
Publish a story
publishStory 4 params → 200401404
GET
/spaces/{space_id}/stories/{story_id}/unpublish
Unpublish a story
unpublishStory 2 params → 200401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ManagementStory (21 properties), Story (19 properties), StoryInput (11 properties), StoryAlternate (6 properties). Each schema is shown below with its type and property counts.

Error
object
Error response returned when an API request fails.
1 property
Story
object
A story is a content entry in Storyblok. It holds structured content defined by a component schema and metadata such as dates, slug, and language alternates.
19 properties
StoryAlternate
object
Metadata about an alternate language version of a story.
6 properties
ManagementStory
object
A story as returned by the Management API, including draft content, workflow state, and editorial metadata not available via the Content Delivery API.
21 properties
Error_2
object
Error response returned when an API request fails.
1 property
StoryInput
object
Input object for creating or updating a story.
11 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

storyblok-stories-api-openapi.yml Raw ↑

Other APIs Storyblok publishes across the network.

Storyblok Webhooks
Storyblok Assets API
Storyblok Collaborators API
Storyblok Components API
Storyblok Datasources API
Storyblok Image Transformation API
Storyblok Links API
Storyblok Spaces API
Storyblok Tags API
Storyblok Webhooks API
Where this information came from

This is an independent, third-party profile of Storyblok Stories API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.