This client is a thin wrapper for the Storyblok API's to use in Node.js and the browser.
npm install storyblok-js-client # yarn add storyblok-js-client
Version to install | Support |
---|---|
Latest storyblok-js-client |
Modern browsers + Node 18+ |
Latest storyblok-js-client + Fetch polyfill like isomorphic-fetch |
Browsers and Node versions with no Fetch API support |
Version 4 storyblok-js-client@4 |
Internet Explorer support |
// 1. Import the Storyblok client
import StoryblokClient from "storyblok-js-client";
// 2. Initialize the client with the preview token
// from your space dashboard at https://app.storyblok.com
const Storyblok = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
});
// 1. Import the Storyblok client
import StoryblokClient from "storyblok-js-client";
const spaceId = <YOUR_SPACE_ID>;
// 2. Initialize the client with the oauth token
// from the my account area at https://app.storyblok.com
const Storyblok = new StoryblokClient({
oauthToken: <YOUR_OAUTH_TOKEN>,
});
Storyblok.post(`spaces/${spaceId}/stories`, {
story: { name: "xy", slug: "xy" },
});
Storyblok.put(`spaces/${spaceId}/stories/1`, {
story: { name: "xy", slug: "xy" },
});
Storyblok.delete(`spaces/${spaceId}/stories/1`, null);
You can import and use the RichTextResolver
directly:
import RichTextResolver from 'storyblok-js-client/richTextResolver'
const resolver = new RichTextResolver()
const html = resolver.render(data)
The old master branch containing version 4.x.y
has been moved to the v4
branch.
We’ve renamed the master
branch to main
and now it contains version 5.0.0.
If you wish to continue using the non Typescript version with axios
, please use version 4
. You can install it by running npm install https://github.com/storyblok/storyblok-js-client.git#4.x.x
.
We added TypeScript to our codebase, improving our code quality and assuring the correct implementation from the client's side. This change will probably break your code, because your Storyblok client's current implementation is possibly sending the wrong types to the source. If you use an IDE to code, you'll be able to hover the problematic cause and see what is being expected from the type. Yet, you can keep using our version without TypeScript.
We removed our dependency on axios in Version 5
. If you want to continue using our SDK with axios, please use version 4
.
The proxy feature was also removed in this version.
Version 5 is using native fetch
API, supported by modern browsers and Node >= 18. If you are using an environment with no fetch
API support, you can use a polyfill like isomorphic-fetch at the very beginning of your app entry point:
import 'isomorphic-fetch'
require('isomorphic-fetch') // in CJS environments
We added retro-compatibility when using resolve_assets: 1
parameter under V2. Now, if you are using our V2 client, you should receive the assets structure just the same as V1.
Parameters
config
Object- (
accessToken
String, optional - The preview token you can find in your space dashboard at https://app.storyblok.com. This is mandatory only if you are using the CDN API.) - (
oauthToken
String, optional - The personal access token you can find in your account at https://app.storyblok.com/#/me/account?tab=token. This is mandatory only if you are using the Management API.) - (
cache
Object, optional)- (
type
String, optional -none
ormemory
)
- (
- (
responseInterceptor
Function, optional - You can pass a function and return the result. For security reasons, Storyblok client will deal only with the response interceptor.) - (
region
String, optional) - (
https
Boolean, optional) - (
rateLimit
Integer, optional, defaults to 3 for management api and 5 for cdn api) - (
timeout
Integer, optional) - (
maxRetries
Integer, optional, defaults to 5) - (
richTextSchema
Object, optional - your custom schema for RichTextRenderer)
- (
- (
endpoint
String, optional)
The Storyblok client comes with a caching mechanism.
When initializing the Storyblok client you can define a cache provider for caching the requests in memory.
To clear the cache you can call Storyblok.flushCache()
or activate the automatic clear with clear: 'auto'.
let Storyblok = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
cache: {
clear: "auto",
type: "memory",
},
});
The Storyblok client lets you pass a function that serves as a response interceptor to it. Usage:
let Storyblok = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
cache: {
clear: "auto",
type: "memory",
},
responseInterceptor: (response) => {
// one can handle status codes and more with the response
if (response.status === 200) {
// handle your status here
}
// ALWAYS return the response
return response;
},
});
One can remove the reponseInterceptor at any time, by calling the function ejectInterceptor
as shown below:
Storyblok.ejectInterceptor()
Exceptions will be thrown as an object with the following structure:
{
message: Error // an Error object with the error message
status: number
response: ISbResponse
}
where,
interface ISbResponse {
data: any
status: number
statusText: string
headers: any
config: any
request: any
}
One should catch the exception and handle it accordingly.
With this method you can get single or multiple items. The multiple items are paginated and you will receive 25 items per page by default. If you want to get all items at once use the getAll
method.
Parameters
[return]
Promise, Objectresponse
path
String, Path (can becdn/stories
,cdn/tags
,cdn/datasources
,cdn/links
)options
Object, Options can be found in the API documentation.
Example
Storyblok.get('cdn/stories/home', {
version: 'draft',
})
.then((response) => {
console.log(response)
})
.catch((error) => {
console.log(error)
})
With this method you can get all items at once.
Parameters
[return]
Promise, Array of entitiespath
String, Path (can becdn/stories
,cdn/tags
,cdn/datasources
,cdn/links
)options
Object, Options can be found in the API documentation.entity
String, Storyblok entity like stories, links or datasource. It's optional.
Example
Storyblok.getAll('cdn/stories', {
version: 'draft',
})
.then((stories) => {
console.log(stories) // an array
})
.catch((error) => {
console.log(error)
})
Parameters
[return]
Promise, Objectresponse
path
String, Path (spaces/*
, ... see more at https://www.storyblok.com/docs/management-api/authentication?utm_source=github.com&utm_medium=readme&utm_campaign=storyblok-js-client)payload
Object
Example
Storyblok
.post('spaces/<YOUR_SPACE_ID>/stories', {
story: {name 'xy', slug: 'xy'}
})
.then((response) => {
console.log(response);
})
.catch((error) => {
console.log(error);
})
Parameters
[return]
Promise, Objectresponse
path
String, Path (spaces/*
, ... see more at https://www.storyblok.com/docs/management-api/authentication?utm_source=github.com&utm_medium=readme&utm_campaign=storyblok-js-client)payload
Object
Example
Storyblok
.put('spaces/<YOUR_SPACE_ID>/stories/1', {
story: {name 'xy', slug: 'xy'}
})
.then((response) => {
console.log(response);
})
.catch((error) => {
console.log(error);
})
Parameters
[return]
Promise, Objectresponse
path
String, Path (spaces/*
, ... see more at https://www.storyblok.com/docs/management-api/authentication)payload
Object
Example
Storyblok.delete('spaces/<YOUR_SPACE_ID>/stories/1', null)
.then((response) => {
console.log(response)
})
.catch((error) => {
console.log(error)
})
Parameters
[return]
Promise, Object returns the Storyblok client
Example
Storyblok.flushCache()
Parameters
callback
Function, Render function to render components of the richtext field
Option 1: Use a switch case definition to render different components:
Storyblok.setComponentResolver((component, blok) => {
switch (component) {
case 'my-custom-component':
return `<div class="my-component-class">${blok.text}</div>`
break
case 'my-header':
return `<h1 class="my-class">${blok.title}</h1>`
break
default:
return 'Resolver not defined'
}
})
Option 2: Dynamically render a component (Example in Vue.js):
Storyblok.setComponentResolver((component, blok) => {
return `<component :blok='${JSON.stringify(blok)}'
is="${component}"></component>`
})
Parameters
[return]
String, Rendered html of a richtext fielddata
Richtext object, An object with acontent
(an array of nodes) field.
Example
Storyblok.richTextResolver.render(blok.richtext)
import StoryblokClient from "storyblok-js-client";
let client = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
});
// Filter by boolean value in content type
client
.get("cdn/stories", {
version: "draft",
filter_query: {
is_featured: {
in: true,
},
},
})
.then((res) => {
console.log(res.data.stories);
});
// Get all news and author contents
client
.get("cdn/stories", {
version: "draft",
filter_query: {
component: {
in: "news,author",
},
},
})
.then((res) => {
console.log(res.data.stories);
});
// Get all content from the news folder
client
.get("cdn/stories", {
version: "draft",
starts_with: "news/",
})
.then((res) => {
console.log(res.data.stories);
});
Following a code example using the storyblok-js-client to backup all content on your local filesystem inside a 'backup' folder.
import StoryblokClient from "storyblok-js-client";
import fs from "fs";
let client = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
});
let lastPage = 1;
let getStories = (page) => {
client
.get("cdn/stories", {
version: "draft",
per_page: 25,
page: page,
})
.then((res) => {
let stories = res.data.stories;
stories.forEach((story) => {
fs.writeFile(
"./backup/" + story.id + ".json",
JSON.stringify(story),
(err) => {
if (err) throw err;
console.log(story.full_slug + " backed up");
}
);
});
let total = res.total;
lastPage = Math.ceil(res.total / res.perPage);
if (page <= lastPage) {
page++;
getStories(page);
}
});
};
getStories(1);
const proxy = {
host: host,
port: port,
auth: {
username: 'username',
password: 'password'
}
}
const storyblok = new StoryblokClient({
...
https: false,
proxy: proxy
})
Read more about proxy settings in axios documentation
To define how to add some classes to specific html attributes rendered by the rich text renderer, you need your own schema definition. With this new schema, you can pass it as the richTextSchema
option when instantiate the StoryblokClient
class. You must follow the default schema to do this.
Below, you can check an example:
import StoryblokClient from "storyblok-js-client";
// the default schema copied and updated
import MySchema from "./my-schema";
let client = new StoryblokClient({
accessToken: <YOUR_SPACE_ACCESS_TOKEN>,
richTextSchema: MySchema,
});
client.richTextResolver.render(data);
If you just want to change the way a specific tag is rendered you can import the default schema and extend it. Following an example that will render headlines with classes:
Instead of <p>Normal headline</p><h3><span class="margin-bottom-fdsafdsada">Styled headline</span></h3>
it will render <p>Normal headline</p><h3 class="margin-bottom-fdsafdsada">Styled headline</h3>
.
import RichTextResolver from 'storyblok-js-client/richTextResolver'
import MySchema from 'storyblok-js-client/schema'
MySchema.nodes.heading = function (node) {
let attrs = {}
if (
node.content &&
node.content.length === 1 &&
node.content[0].marks &&
node.content[0].marks.length === 1 &&
node.content[0].marks[0].type === 'styled'
) {
attrs = node.content[0].marks[0].attrs
delete node.content[0].marks
}
return {
tag: [
{
tag: `h${node.attrs.level}`,
attrs: attrs,
},
],
}
}
let rteResolver = new RichTextResolver(MySchema)
let rendered = rteResolver.render({
content: [
{
content: [
{
text: 'Normal headline',
type: 'text',
},
],
type: 'paragraph',
},
{
attrs: {
level: 3,
},
content: [
{
marks: [
{
attrs: {
class: 'margin-bottom-fdsafdsada',
},
type: 'styled',
},
],
text: 'Styled headline',
type: 'text',
},
],
type: 'heading',
},
],
type: 'doc',
})
console.log(rendered)
- Storyblok & Javascript on GitHub: Check all of our Javascript open source repos;
- Technology Hub: We prepared technology hubs so that you can find selected beginner tutorials, videos, boilerplates, and even cheatsheets all in one place;
- Storyblok CLI: A simple CLI for scaffolding Storyblok projects and fieldtypes.
-
Bugs or Feature Requests? Submit an issue;
-
Do you have questions about Storyblok or you need help? Join our Discord Community.
Please see our contributing guidelines and our code of conduct. This project use semantic-release for generate new versions by using commit messages and we use the Angular Convention to naming the commits. Check this question about it in semantic-release FAQ.