Addon API

Core Addon API

This is the core addon API. This is how to get the addon API:


Get an instance to the channel where you can communicate with the manager and the preview. You can find this in both the addon register code and your addon’s wrapper component (where used inside a story).

It has a NodeJS EventEmitter compatible API. So, you can use it to emit events and listen for events.


This method allows you to register an addon and get the storybook API. You can do this only in the Manager App. See how we can use this:

Now you'll get an instance to our StorybookAPI. See the api docs for Storybook API regarding using that.


This method allows you to add a panel to Storybook. (Storybook's Action Logger is a panel). You can do this only in the Manager App. See how you can use this method:

The render function is called with active and key.

When the panel is in focus in the UI, the active will be true.

As you can see, you can set any React Component as the panel. Currently, it's one line of text. But you can do anything you want. It's a good practice to specify the panel title with the title key. You can use any plain text with it.

makeDecorator API

Use the makeDecorator API to create decorators in the style of the official addons. Like so:

The options to makeDecorator are:

  • name: The name of the export (e.g. withFoo)
  • parameterName: The name of the parameter your addon uses. This should be unique.
  • skipIfNoParametersOrOptions: Don't run your decorator if the user hasn't set options (via .addDecorator(withFoo(options)))) or parameters (.add('story', () => <Story/>, { foo: 'param' }), or .addParameters({ foo: 'param' })).
  • allowDeprecatedUsage: support the deprecated "wrapper" usage (.add('story', () => withFoo(options)(() => <Story/>))).
  • wrapper: your decorator function. Takes the storyFn, context, and both the options and parameters (as defined in skipIfNoParametersOrOptions above).

πŸ’‘ Note:If the story's parameters include { foo: { disable: true } } (where foo is the parameterName of your addon), your decorator will not be called.

Storybook hooks

Writing addons can be simplified a lot by using these Storybook hooks:


It allows full access to the entire storybook state. Your component will re-render whenever the storybook state changes.

If you use this, remember your component will be re-rendered a lot, and you may need to optimize for that using React.memo or useMemo or PureComponent.


It allows full access to the storybook API.

Details on the Storybook API are further down.


Allows for both setting subscriptions to events and getting the emitter for emitting custom events unto the channel.

The messages can be listened to on both the iframe and the manager side.


Extremely useful for addons that need to persist in some form of state.

Storybook may unmount your addon component, and so keeping local state might not work well.

Also, some addons consist of multiple parts, some parts being in a panel, some in the toolbar, etc.

With this hook, addons can get access to the same portion of the state, persisted even if the components are unmounted.


This hook gets you the current story's parameter.

If the parameter isn't set, the default value (second argument) is returned instead.


Extremely useful hook for addons that rely on Storybook Globals.

It allows you to retrieve and update any Storybook Globals you want.

If you use this hook, remember that your component will render a lot, and you may need to optimize for that using React.memo or useMemo or useCallback.


A handy Storybook hook that you can use in your addon if you need to read or update args.

Storybook API

Storybook API allows you to access different functionalities of Storybook UI. You can move an instance to the Storybook API when you register an addon.

Let's have a look at API methods.


With this method, you can select a story via an API. This method accepts two parameters.

  1. story kind name
  2. story name (optional)

Let's say you've got a story like this:

This is how you can select the above story:


Same as selectStory, but accepts a story inside current kind as the only parameter:


This method allows you to set query string parameters. You can use that as temporary storage for addons. Here's how you define query params:

πŸ’‘ Note: If you need to remove a query param, use null for that. For example, let's say we need to remove the bbc query param. See below how to do it:


This method allows you to get a query param set by the above API setQueryParams. For example, let's say we need to get the bbc query param. Then this how we do it:


This method allows you to get the application URL state with some changed params. For example, if you want to get a link to a particular story:

api.on(eventName, fn)

This method allows you to register a handler function called whenever the user navigates between stories.

Add Storybook to your project in less than a minute to build components faster and easier.
Learn Storybook with in-depth tutorials that teaches Storybook best practices. Follow along with code samples.
The MIT License (MIT). Website design by @domyen and the awesome Storybook community.
Get news, free tutorials, and Storybook tips emailed to you.

Maintained by
Continuous integration by
Hosting by