🍪 Cookie Notice

We use cookies to learn how you interact with our content, and show you relevant content and ads based on your browsing history. You can adjust your settings below. Here's our policy.

Cookie settings
Skip to main content

JoyConf 2026 is back. Content Confidence. Human Connection. Save your spot!

NewPremium Plan

OAuth 2.0 Scoped Grants

  • Extensions
  • Security
  • Developer Experience
Books and Storyblok Logo

OAuth 2.0 Scoped Grants are now available for custom integrations connecting to the Management API. Instead of relying on long-lived personal access tokens, integrations can request clearly defined permissions that users review and approve on a consent page. Scopes are set at the resource-action level using a publish, write, and read hierarchy, with per-space selection, short-lived access tokens, rotating refresh tokens, and immediate revocation.

OAuth 2.0 Scoped Grants are available on Premium and Enterprise.

[Link here]

Related Updates

New

Mobile SDKs: Native support for Android and Apple platforms

  • User Experience
  • Workflows
  • Developer Experience

Storyblok now offers official, first-party SDKs for native mobile development. No more building your own API integration, rendering layer, or offline handling from scratch. What's new: Android SDK: built for Jetpack Compose. Includes story fetching, block and rich text rendering, and offline support.Android Tech Guide: full walkthrough, including best-practice patterns for dynamic navigation with the Navigation 3 library, internationalization, and on-device visual preview for debug app builds.Apple SDK: built for SwiftUI, covering iOS, macOS, and tvOS. Includes story fetching, rich text rendering, and offline support.Apple Tech Guide: full walkthrough, including best-practice patterns for block rendering, dynamic navigation, internationalization, and on-device visual preview for debug app builds.

New

Type-Safe Schemas with @storyblok/schema

  • User Experience
  • Developer Experience

Define fields, blocks, and datasources as type-safe TypeScript objects and keep your code and content model in sync automatically. We give you a schema-driven way to manage content models: @storyblok/schema. Paired with the Storyblok CLI, it lets you define fields, blocks, and datasources directly in code using defineField(), defineBlock(), and defineDatasource(), then push those definitions to your space with schema push. Until now, content models lived in the UI and Management API, and code only consumed them via storyblok types generate. That's an inverted flow: types are generated for code instead of from code, an accidental change in the block library can break the frontend without warning, and versioning the structures your code depends on requires workarounds. @storyblok/schema flips this around, where your repo becomes the single source of truth, and both your space and your frontend types stay in sync with it. Highlights: Bootstrap from an existing space: storyblok schema init generates schema objects for all your current components, similar to types generate.Type-safe definitions: defineField(), defineBlock(), and defineDatasource() catch mistakes at compile time.Push straight from your terminal: storyblok schema push (with a --dry-run option) applies your schema files to the space.Framework-ready types: the BlockContent<TBlock, TBlocks> utility type extracts exactly the props a Vue or React component needs from a schema object.Version-controlled content models: schemas are plain TypeScript files, so diffs, PRs, and rollbacks work the way they do for the rest of your code. Give it a try and tell us what works and what's missing! [@storyblok/schema package] [Learn More]