Bufferapp
/1/* version retirement
Deprecated, no dateSubscribe to BufferappShare
Bufferapp deprecated /1/* without giving a shutdown date yet.
Calls it hits
/1/*
What to use instead of these calls
Move to the GraphQL API: POST https://api.buffer.com with Authorization: Bearer <API key> (or OAuth 2.0 with PKCE for apps acting for other users); see Buffer's REST API Migration guide.
In Bufferapp's words
If you've been using our REST API ( api.bufferapp.com/1/ ), this guide will help you move over to the GraphQL API. It's faster to work with, returns only the data you need, and supports the core functionality of the legacy API offering.
Facts
- API
- Bufferapp
api.bufferapp.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bufferapp's own pages
Questions
When does this change take effect?
Bufferapp deprecated /1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bufferapp has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.