We’ve always believed in building in public at Buffer — and if you’ve been around a while, you’ll know we You can also find out more about the following: Meaning it
Over the past decade, we have worked with transparency and community involvement at our core. It’s for this reason that I’m so excited to give you an inside look at the public API we are bringing back.
Amanda, I am the Product Manager who is leading this initiative. I would like to share with you the big picture of what the API will be used for, why it was built, and the next steps.
Buffer API – the origin story
We first launched Buffer’s public API in 2012 with a small but mighty group of 15 integrations — think Pocket, IFTTT, and other early web favorites. A few of the now competing social tools were originally Buffer integrations.
The API we built was built using REST, the standard of that time. It allowed us to allow developers to schedule posts or manage profiles. Our privacy was a priority from the start and we created documentation to assist people in getting started. In 2019, the API was used by over 47,000 users.
The landscape was very different by that time. In response to privacy scandals, such as Cambridge Analytica’s, many social networking platforms, including Meta (Facebook), Pinterest and LinkedIn (formerly Twitter), have introduced tighter privacy and terms of services. In order to be compliant, we tightened our API use.
Around this time our internal priorities also changed. We decided to stop allowing new applications because we knew we couldn’t offer the dev experience we wanted — and our partners deserved — without a bigger investment.
It’s a comeback!
Was it the bigger investment that I spoke of? It’s time. There are a few big reasons we’re investing in rebuilding Buffer’s API — and they all come back to doing right by our community.
Here’s a deeper look:
This is something we want to do with you
Transparency, collaboration and openness have been part of the DNA since our inception. Rebuilding the API gives us a chance to create something that’s more powerful, more accessible, and genuinely useful — with feedback and input from the people who’ll actually use it.
Our goal is to open up new doors for independent devs and small businesses
We are committed to helping creators and small businesses grow sustainably. A modern API removes barriers and opens the door for folks to customize Buffer to their needs — or even build something entirely new on top of it. It’s great to see.
We can’t — and shouldn’t — build everything ourselves
Our users have edge cases, workflows, and needs that don’t always fit neatly into our core roadmap — and that’s okay! Our community can build tools without having to wait on us. A flexible and developer-friendly API will allow others to create the tools that they need.
A powerful, adaptable UI is what we want
As we rebuild, we’re thinking ahead to a future where Buffer’s UI can flex and adapt based on what users actually need — no bloat, no clutter. This is made possible by a better API.
It’s not just about the tech.
The old API had become outdated. Rebuilding it gives us a stronger, more secure foundation to work from — one that’s scalable, well-documented, and ready for whatever comes next (AI tools, automation, you name it).
We’re developing a new API to help you.
As we rebuild the API, we’re thinking about two main groups of people who’ll be using it — both equally important, and both doing really exciting things.
1. Power users personalizing Buffer
These folks are customizing Buffer for The following are some examples of how to get started: own workflows — think social media managers, marketers, or just super-organized creators who want things to run their way.
We want to give them the ability to get creative and save time using our API, whether it is for automation, tools that don’t require code, or custom dashboards. No formal developer background needed.
Andrew Yates is one of our developers who created Alpenglow as a hobby. Alpenglow is a tool that helps you pinpoint when a sunrise, sunset or other natural phenomenon will occur in your location.
This workflow was created by connecting Buffer to Alpenglow using the API.
- App users can upload sunrise and sunset photos.
- Buffer drafts receives the image and caption if they have given permission.
With this relatively simple set-up, Andrew had over 3,000 drafts waiting for him in Buffer — enough for more than two years of content, he predicts.
Incredible, right?
2. Integrations built by developers for other companies
Then there’s the folks building third-party integrations — tools that work You can also find out more about You can buffer and serve whole communities or organisations. These projects require more depth in terms of technical expertise: authentication, error-handling, privacy compliance and the like.
When? “developer” This definition, which used to refer to someone who was familiar with a terminal’s layout and functions, is changing rapidly.
Thanks to AI and low-code tools, the developer community is getting more diverse — which is exactly why we’re focused on making our docs, tooling, and onboarding super approachable. More on this coming soon!)
Keep an eye on this page for updates
We are not only strengthening our foundations by rebuilding the API. Our commitment to Buffer’s community is increasing. It’s more than just code. It is all about creating an open and flexible platform, which gives small business owners, developers, and users of everyday life the tools to create what they want.
This is something I’m very excited about! You can ask any question in the comments section. You can get started as quickly as you like if you are a programmer. register here for early access. 👀
Soon, we’ll have more to share!
