Since its debut in 2012, you’ve used the embedded timeline to delight your users with engaging, interactive Tweets about news, sports, politics, and more. In March, we upgraded the embedded timeline to a modern new design that beautifully showcases Tweets across your desktop and mobile sites. Now, we’re excited to announce that we’ve made it easier than ever to add these rich, responsive Tweet displays directly to your website or CMS.
Whether you want to programmatically generate thousands of timelines at once, or you’re just looking for the quickest way to add a single Twitter timeline to your site, we’ve got you covered. With factory functions, you can now easily generate timelines for any web app, whether you want one timeline or one million. You can also use our new oEmbed API to seamlessly integrate profile, list, like, or collection timelines directly into your CMS. Or, you can go straight to publish.twitter.com to customize your own embedded timeline display and get the code you need to copy and paste into your site; no Computer Science degree required.
Retrieving embed code via publish.twitter.com
As part of these improvements, we’ve also removed the need to create and save widgets to your account. Of course, if you already have timeline widgets, you can always access them in your Twitter settings. But, going forward, you won’t need to log in to create or configure embedded timelines, and you’ll never need another widget ID again. All you need is a public profile, list, like, or collection URL to get started. Check out our documentation or go to publish.twitter.com for more information. And, as always, by embedding Twitter content in your website or app, you are agreeing to the Developer Agreement and Developer Policy.
We love seeing the stories that you tell with Tweets, and we’re excited to continue making it even easier to engage your users with dynamic displays that fit as seamlessly into your workflows as they fit into your websites. We look forward to hearing your feedback in the forums and by mentioning @TwitterDev, and we can’t wait to see what you build next with these new tools.
Did someone say … cookies?