Media hosting for the Buffer API
Post images through the Buffer API, without hosting them.
Send Media Saver a file and your post. It stores the image, schedules the post in your Buffer account, and deletes the file once it has been published.
Request
curl -X POST https://mediasaver.si/api/v1/posts \ -H "Authorization: Bearer ms_live_••••••••" \ -F "file=@launch.jpg" \ -F "channelId=YOUR_CHANNEL_ID" \ -F "text=We just shipped it." \ -F "dueAt=2026-11-05T10:00:00Z"
Response, 201 Created
{
"postId": "6ae578a0b84259308bbbe3d6",
"status": "scheduled",
"dueAt": "2026-11-05T10:00:00.000Z"
}The Buffer API has no upload endpoint.
Every image must already sit at a public link you host, and it has to stay there until the post goes out, which can be days later.
Easy in a browser. Hard in an automation. Media Saver is that host.
How it works
Connect Buffer
Approve Media Saver on Buffer’s own screen. Your login stays with Buffer, and tokens are encrypted at rest.
Send a file and your post, in one request.
Your API key, the image, the text, the channel and an optional time. Media Saver hosts the file and creates the post in your Buffer account.
Published, then cleaned up
Buffer publishes on schedule. Once the post is sent, Media Saver deletes the file, so nothing piles up.
Built for the tools that post for you.
n8n / Zapier / Make / AI agents / your own scripts
Why you can trust it
Files live only as long as needed
Each file keeps a stable public link until its post is sent, then it is deleted. When in doubt, the file is kept, never removed early.
Buffer stays in charge
Your queue, schedule and publishing all run in Buffer. Media Saver only fills the media gap.
Secure by default
OAuth with PKCE, encrypted tokens, hashed API keys and unguessable file names.