Connector
Storyblok Connector
Fetch content from the Storyblok headless CMS over a REST connection Rapidi sets up with you, without writing code.
Rapidi connects to Storyblok, the headless CMS, through its REST Web Service connection, signed in with a Storyblok API token. Rapidi builds the JSON schema for the connection from your API documentation and the scope of the integration, and Read Design then loads the fields you can map. The documented setup fetches stories from Storyblok.
- What it connects to
- Storyblok, the headless content management system, through its API.
- Which way the data moves
- The documented setup fetches content from a Storyblok endpoint. Ask us about anything else.
- What you need
- The Storyblok endpoint for the content, a Storyblok API token, and the JSON schema Rapidi builds for you.
What does this connector actually do?
| What Storyblok is | A headless CMS that lets developers create content and distribute it to web, mobile or IoT, with visual editing for content creators. |
|---|---|
| How it connects | The REST WebService connection in MyRapidi, pointed at the Storyblok endpoint that holds the content you need, such as the stories of a space. |
| How it signs in | Token authentication. The Storyblok API token goes in the Password field of the connection. |
| How fields are defined | A JSON schema that Rapidi builds from your API documentation and the scope of the integration. Its address goes in the Metadata URL field. |
| Security | Use SSL is switched on for the connection. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| Checks before go-live | Test confirms Rapidi can reach Storyblok, and Read Design loads the fields from the schema. |
How do you set up the Storyblok connection?
Setup happens in MyRapidi, once Rapidi has built the schema.
- Under Connections, click New Connection and select REST WebService.
- Give the connection a clear name in Description.
- Choose Token as the authentication type.
- In Server Connect, enter the Storyblok endpoint for the content you need, for example the stories endpoint of your space.
- Put your Storyblok API token in the Password field.
- Put the JSON schema address in the Metadata URL field.
- Tick Use SSL, click Test, then Read Design to finish.
Who builds the schema?
Rapidi does. There is no single standard for how REST APIs describe their data, so the JSON schema is built from your Storyblok API documentation and the scope of the integration you agree with us. Once it is in place, Read Design turns every field it describes into something you can map.
| Item | Who provides it | Where it goes |
|---|---|---|
| Storyblok endpoint | You, from your Storyblok space | Server Connect |
| Storyblok API token | You, from Storyblok | Password |
| JSON schema | Rapidi, from your API documentation and scope | Metadata URL |
A new REST connection arrives with a RapidiConnector attached. For a service Rapidi can reach over the internet, you delete it to let Rapidi connect directly.
Which other systems connect the same way?
Storyblok runs on the generic REST Web Service connection, the same one that reaches Workday and Dayforce.
Connector
REST Web Service
The generic REST connection this connector is built on, for any system with a REST API.
APIs and Protocols
Connector
Workday
HR data over the same REST and JSON schema pattern, usually going into an ERP or CRM.
Business Apps
Category
Business Apps
The other business systems Rapidi connects to your ERP or CRM.
See the category
Where do you go next?
Connectors
Every system Rapidi connects to
The full list, A to Z, with versions and how each one connects.
All connectors
Connector
REST Web Service
The generic REST connection this connector is built on, for any system with a REST API.
APIs and Protocols
Pricing
What Rapidi costs
Four plans, priced per subscription rather than per connector. Adding Storyblok does not change the licence.
Plans
Your setup
Ask about your Storyblok content
Tell us which content you need and where it has to go, and we will say plainly what the schema and setup involve.
Talk to a consultant
Frequently asked questions
Can Rapidi connect to Storyblok?
Yes. Rapidi connects to Storyblok through its REST WebService connection, signed in with a Storyblok API token.
What does the connection read from Storyblok?
The content at the Storyblok endpoint you enter in Server Connect, for example the stories of a space. The JSON schema defines which fields of that content can be mapped.
Who builds the JSON schema?
Rapidi builds it, based on your Storyblok API documentation and the scope of the integration. You enter its address in the Metadata URL field.
How does the connection sign in?
With token authentication. Choose Token as the authentication type and put your Storyblok API token in the Password field.
Does anything have to be installed on our side?
Not for a service Rapidi can reach over the internet. A new REST connection arrives with a RapidiConnector attached, and you delete it to let Rapidi connect directly.
How often does the data move?
On a schedule you set. The shortest interval comes from your plan, from one hour on Entry down to one minute on Unlimited.
What does the Storyblok connector cost?
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding Storyblok does not change the licence.
Is your content in Storyblok?
Tell us which content you need and where it has to go, and we will tell you plainly what the setup involves.