oEmbed Server

Making it easier to embed your Knight Lab stories.

There's really no reason to visit this page, but in case you ended up here, this is what's going on.

oEmbed is a system to help third party sites embed content. It's the protocol that supports, for some CMSes, the ability to just put a URL to a Knight Lab Timeline (or other embeddable content) on a single line, and have the full story pulled in.

Each CMS is different; typically the adminstrator needs to do some configuration. Some people pay for service from Embedly to simplify the configuration. Embedly supports several Knight Lab story types, and we will try to keep them up to date as we add new services. It's because of Embedly that you can embed our stories on Medium.com. (See our blog post announcing that.)

Using this server directly

This server handles a number of oEmbed URL schemes. For all of them, use the same endpoint: https://oembed.knightlab.com. If no url parameter is provided, this instructional page appears.

If the url parameter value matches one of the following patterns, a JSON response will be returned. Otherwise, the server will return a 404 Not Found error.

This endpoint also supports the format, maxwidth, and maxheight request parameters. Valid values for format are json and xml. If no format is specified, JSON is the default response type.

TimelineJS ^https://cdn.knightlab.com/libs/timeline3/.+$
StoryMapJS ^https://uploads.knightlab.com/storymapjs/.+$
JuxtaposeJS ^https://cdn.knightlab.com/libs/juxtapose/.+$
SceneVR ^https://uploads.knightlab.com/scenevr/.+$
StoryLineJS ^https://cdn.knightlab.com/libs/storyline/.+$
They Draw It ^https://theydrawit.mucollective.co/vis/.+$