Migrate from Buffer's legacy REST API to SocialCannon
Buffer's legacy REST API stops on 1 February 2027. Map the legacy posting calls to their SocialCannon calls, see which have no equivalent, replace the queue, reconnect accounts and cut over without posting twice.
Updated · 8 min read
Buffer is retiring its legacy REST API, the one at api.bufferapp.com/1/, on 1 February 2027. Buffer says legacy requests will no longer return data after that date, so any script, plugin or integration still calling /updates/create.json needs a new route before then. Buffer’s replacement is a GraphQL API with a single endpoint, and its own migration guide (opens in a new tab) covers that route. This guide covers the other one: moving the same integration to SocialCannon, which is also a REST API. The core calls map directly: list accounts, and create, read, edit and delete posts. Queue management and a few other legacy calls have no equivalent, and the table below marks each one. The authentication, the field names and the one-request-per-account rule change.
Check that this move suits you
SocialCannon is a publishing API first. Before you rewrite anything, check three things.
- Networks. SocialCannon publishes to Facebook, Instagram, LinkedIn, TikTok, YouTube and X. If your integration posts to another network through Buffer, such as Pinterest, Mastodon or Google Business Profile, keep those channels in Buffer and check Buffer’s new API for them.
- The queue. If your integration relied on Buffer’s queue and posting schedules to choose the time of each post, note that SocialCannon has no queue: every post carries its own time, or publishes at once. The queue section below shows the replacements.
- History. SocialCannon does not import the posts Buffer already sent or their statistics. A migration moves what you publish from now on, so export anything you want to keep from Buffer first.
Legacy endpoint map
Legacy paths are relative to https://api.bufferapp.com/1. SocialCannon paths are relative to https://socialcannon.app. A Buffer profile is a SocialCannon account, and a Buffer update is a post.
| Buffer legacy call | SocialCannon call | What changes |
|---|---|---|
access_token | POST /api/v1/auth/token | Client credentials instead of a user token. Send the result as a Bearer header; it lasts one hour. |
GET /user.json | GET /api/v1/auth/identity | The nearest call, not an equivalent: it returns the API client the token belongs to, with no user profile. |
GET /profiles.json | GET /api/v1/accounts | Lists connected accounts with their IDs. |
GET /profiles/:id.json | GET /api/v1/accounts/:id | Reads one account. |
POST /updates/create.json | POST /api/v1/posts | One request per account, JSON body. Leave out scheduledAt to publish now. |
GET /profiles/:id/updates/pending.json | GET /api/v1/posts?status=scheduled&accountId=… | Cursor pagination instead of page and count. |
GET /profiles/:id/updates/sent.json | GET /api/v1/posts?status=published&accountId=… | Lists posts published through SocialCannon only. |
GET /updates/:id.json | GET /api/v1/posts/:id | Includes the network post ID and URL once published. |
POST /updates/:id/update.json | PATCH /api/v1/posts/:id | Edits the text or the time of a draft or scheduled post. |
POST /updates/:id/destroy.json | DELETE /api/v1/posts/:id | Cancels a draft or scheduled post. For a post already published, SocialCannon must delete it on the network first: the API reference describes the strictCompensation body, and the call is refused where that deletion is unsupported or fails, so check the response. |
GET /updates/:id/interactions.json | GET /api/v1/posts/:id/engagements | Comments on supported networks, with the engagements:read scope. X returns stored replies only. |
GET /info/configuration.json | GET /api/v1/platforms | The nearest call, not an equivalent: public JSON listing what each platform supports, no token needed. |
| Posting schedules, reorder, shuffle, move to top | No equivalent | There is no queue. See the queue section below. |
POST /updates/:id/share.json | No equivalent | SocialCannon has no matching call. |
GET /links/shares.json | No equivalent | No call returns share counts for a URL. On Pro and above, post analytics report shares for each post where the network provides them. |
Step 1: Replace the access token
The legacy API took a user’s OAuth access token, usually in the query string. SocialCannon uses the OAuth 2.0 client credentials flow: your server exchanges a client ID and secret for a short-lived bearer token. Create a free account, then copy the client ID and generate a secret under Settings → API Keys. The secret is shown once, so store it in your server’s secret store. If you already use a SocialCannon secret elsewhere, reuse it: pressing Generate API Secret replaces it, and anything still using the old one stops working.
curl -X POST https://socialcannon.app/api/v1/auth/token \
-H "Content-Type: application/json" \
-d '{
"grant_type": "client_credentials",
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET"
}'The token is in data.access_token and is valid for one hour; request a new one when it expires. Listing accounts needs the accounts:read scope, reading posts needs posts:read, and creating or editing them needs posts:write. Add media:upload to upload images and videos, posts:delete to cancel posts, accounts:write to create connect links, engagements:read to read comments and analytics:read for auto-scheduling. You set scopes in the API Scopes card on the same tab, then request a new token, because a token keeps the scopes it was issued with.
Step 2: Reconnect your accounts
Connections cannot be copied out of Buffer. Each network grants access to one application, so the owner of each account signs in to the network once more and approves SocialCannon. In the dashboard that is the Accounts page. From code, POST /api/v1/accounts/connect-token with a body such as { "platform": "linkedin" } returns a connectUrl that is valid for ten minutes; open it in the account owner’s browser.
Then list the accounts and keep a table from each old Buffer profile ID to its new SocialCannon account ID. Every later step uses it.
curl https://socialcannon.app/api/v1/accounts \
-H "Authorization: Bearer TOKEN"Step 3: Replace updates/create
A typical legacy call posted one text to two profiles at a set time:
curl -X POST "https://api.bufferapp.com/1/updates/create.json?access_token=TOKEN" \
--data-urlencode "text=Our autumn update is live." \
--data-urlencode "profile_ids[]=PROFILE_ID_1" \
--data-urlencode "profile_ids[]=PROFILE_ID_2" \
--data-urlencode "media[photo]=https://example.com/autumn-update.jpg" \
--data-urlencode "scheduled_at=2026-12-01T09:00:00Z"With SocialCannon, send one request for each account, with a JSON body:
curl -X POST https://socialcannon.app/api/v1/posts \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: autumn-update-ACCOUNT_ID_1" \
-d '{
"accountId": "ACCOUNT_ID_1",
"content": "Our autumn update is live.",
"mediaUrls": ["UPLOADED_MEDIA_URL"],
"scheduledAt": "2026-12-01T09:00:00Z"
}'A scheduled post can only use media uploaded to SocialCannon; a file hosted elsewhere is refused with 400 SCHEDULED_MEDIA_EXTERNAL_REQUIRES_UPLOAD. Upload each file first, which needs the media:upload scope. POST /api/v1/media/upload-init with the file’s name, type, size and the accountId returns a signed uploadUrl; PUT the file there with the requiredHeaders it lists, then send its publicUrl to POST /api/v1/media/upload-complete. Put the url that call returns in mediaUrls, and upload again for each new post, because a file is kept only while a post can still publish it.
| Legacy field | SocialCannon field | Notes |
|---|---|---|
profile_ids[] | accountId | One account per request. Loop over your accounts. |
text | content | Each network keeps its own length limit. |
media[photo] | mediaUrls | URLs of the image or video files, uploaded to SocialCannon first for a scheduled post. Put a link you want to share in the content. |
scheduled_at | scheduledAt | An ISO 8601 time in UTC, up to 30 days ahead. |
Send a different Idempotency-Key for each post. If a response is lost, repeat the identical request with the same key: you get the original post back, or a 409 with its ID if it is still in progress or needs recovery, and never a second post. After a 409, read that post with GET /api/v1/posts/:id before you create another.
Some networks need more than text. Instagram and TikTok need media, YouTube publishes video, and TikTok needs a privacy level on every post. The cross-posting guide lists the rules for each network.
Step 4: Replace the queue
If your integration relied on Buffer’s queue to choose times, pick the replacement that matches what the queue did for you.
| What the queue did | SocialCannon replacement |
|---|---|
| Sent each post at the next free slot | Compute the time in your code and send it as scheduledAt, up to 30 days ahead. |
| Chose a good time for you | On Pro and above, send "scheduledAt": "optimal" when you create a post, or spread several posts over the next seven days with POST /api/v1/posts/auto-schedule. That call needs the posts:write and analytics:read scopes and its own Idempotency-Key header. |
| Posted on a fixed weekly pattern | Create a recurring series, which repeats a post on a daily, weekly or monthly rule in your time zone. |
| Posted new articles from a blog | Create an RSS feed, which turns each new entry into a post, with review before publishing by default. |
Series and feeds are enabled for each workspace separately, and a workspace without one gets 404 FEATURE_DISABLED. Both are described in recurring posts and RSS feeds with one API. To see what is planned, GET /api/v1/calendar with a startDate and an endDate returns the posts in that range with a count for each day and the days that have none. The range is up to 7 days on Free and 90 on Pro, and 365 on Agency and Enterprise.
Step 5: Test, then cut over
- Test without posting. Use
sandboxas theaccountId. The sandbox simulates a publication and contacts no social network, so you can check your requests end to end. It does not check media, so confirm a scheduled post with uploaded media on the real account in the next steps. - Empty the Buffer queue for one account. A post left queued in Buffer and also scheduled in SocialCannon is published twice. Let Buffer’s remaining posts for that account go out, or delete them, before you create the same posts in SocialCannon.
- Move that account. Schedule its next posts in SocialCannon and confirm one publishes.
- Move the rest the same way, emptying each Buffer queue first, then remove the Buffer token from your configuration.
If a scheduled post fails, it keeps a plain-English reason, and POST /api/v1/posts/POST_ID/retry tries it again after you fix the cause. The error reference gives the safe next action for every code.
Limits and price
The Free plan includes unlimited posts and scheduling for one connected account and 30 API requests a minute. Pro raises that to 20 accounts and 300 requests a minute. Publishing to X needs a paid plan and has an allowance for each billing period. The pricing page has every plan, and SocialCannon and Buffer compared sets the two APIs side by side.
Next steps
The API reference describes every endpoint used here. Scheduling posts with one REST API covers what happens at publish time in more detail. If an AI assistant will do the posting, read the MCP guide.
Frequently asked questions
- When does Buffer's legacy REST API stop working?
- Buffer announced that the legacy REST API at api.bufferapp.com/1/ is retired on 1 February 2027, after which its endpoints no longer return data. This was read from Buffer's announcement on 19 November 2026; check Buffer's own pages for the current date.
- Do I have to rewrite my integration in GraphQL?
- Only if you move to Buffer's new API, which is GraphQL. SocialCannon is a REST API with JSON bodies, so an integration built on Buffer's legacy REST calls keeps the same operations: one request to list accounts, one to create a post, one to edit it and one to delete it. The authentication and field names change, and each post goes to one account per request.
- Can I move my connected accounts and queued posts across?
- No. Each account owner signs in to the social network again to connect it to SocialCannon, and queued posts are created again as scheduled posts. Empty the Buffer queue for an account before you schedule the same posts in SocialCannon, or they are published twice.
- Does SocialCannon have a queue like Buffer?
- No. Every post carries its own scheduledAt time or publishes at once. On Pro and above you can send "optimal" to have a time chosen for you. Recurring series and RSS feeds cover posts that repeat, on every plan, in workspaces that have them enabled.
- Which networks can I move?
- Facebook, Instagram, LinkedIn, TikTok, YouTube and X. X needs a paid plan. For a network SocialCannon does not publish to, such as Pinterest or Mastodon, keep that channel in Buffer and check whether Buffer's new API covers it.
Start with a free account
Free includes one connected account, unlimited posts and scheduling, and a sandbox for testing. Some features in this guide need Pro; the pricing page lists what each plan includes.