Buffer API Change Logs

Buffer API news and updates all in one place.

For any questions about our API, please feel free to reach out to us at partnerships@buffer.com.

September 8, 2020: API deprecation

On September 8, we began limiting third party usage of the Buffer API in order to protect the relationships we have with our social network partners. Having reviewed usage of the Buffer API and the commitments we’ve made to Facebook, Instagram, Twitter, Pinterest, and LinkedIn, we’ve determined that we can no longer permit certain usage of the Buffer API. We’re grateful to our partners for being a part of Buffer’s API in the past and apologize for any disruptions this might cause your community or clients. As part of this change, some accounts have had their access to the Buffer API suspended.

October 14, 2019: New application registration closed

As of this date, Buffer is no longer accepting any new developer applications for the Publish API.

The Buffer Publish API has been an open platform for many years, but we feel that in its current form, the API does not provide the level of quality of developer experience and functionality coverage for developers to build applications that compliment the experience we provide for our users through our first party applications.

The API will remain open to all developers that have existing applications. If you are an existing developer who is seeking additional information please contact our team at partnerships@buffer.com.

February 19, 2019: Important Twitter changes to the Buffer API

To Our Valued Buffer Partners:

In order to comply with the updated 2019 Twitter Developer Policy, we are making a few changes to Twitter content that we provide to our partners and third parties.

We are only able to provide, distribute, and allow download of Tweet IDs, Direct Message IDs, and/or User IDs. Any additional Twitter content beyond these IDs will be redacted from the Buffer API effective February 19, 2019.

The following endpoints will be affected:

/profiles and /profile/:id will no longer return the parameters for all Twitter profiles:

• service_username
• formatted_username
• avatar
• avatar_https
• cover_photo
• statistics

/updates/:id and /profiles/:id/updates/sent will not longer return the parameters:

• text
• text_formatted
• media
• extra_media
• service_link
• statistics
• retweet

To comply with Twitter’s Developer Policy, if you would like to retrieve any of the redacted information you can communicate directly with the Twitter API utilizing the following IDs in your requests:

• profiles, /profile/:id will return the service parameter set to "twitter" and the service_id parameter which corresponds to a Twitter user_id.

More information on user lookup here

• /updates/:id, /profiles/:id/updates/sent will return the profile_service parameter set to "twitter" and the service_update_id which corresponds to a Twitter Tweet ID.

More information on Tweet lookup here

Thank you so much for your understanding as we implement these important changes. Please feel free to email us at partnerships@buffer.com with any questions you might have.