Document LinkedIn character limit and Unicode handling in Buffer docs

Buffer enforces a 1,248-character limit for LinkedIn posts (based on tests), but this isn't documented anywhere in Buffer's help center or API docs. Users only discover it when a post fails to schedule.This is especially confusing because:LinkedIn's own limit is 3,000 charactersBuffer's limit is measured in UTF-16 characters, not visible charactersUnicode bold/italic characters (U+1D400–U+1D7FF, commonly used for LinkedIn formatting) count as 2 characters each, so the effective visible character limit is significantly lower than 1,248Request: Add a documentation page or help article...

Image assets for API

it’s a real blocker that any image to attach thorugh the API must already be hosted online somewhere. It would be ideal if the API had an option to upload an image asset, whish of course when could be purged after post was created.

Copy media to Buffer storage after post creation

After successful createPost, please ingest/copy media to Buffer-hosted storage so external source URLs can be safely deleted. Currently, deleting source files too early may break media in scheduled posts. This makes external storage management complex and fragile.

Support video media in createIdea (Public API)

Please add full video support for createIdea. Text and image ideas work, but video ideas fail with: "Video uploads are not supported via the public API. Please use image, gif, or document types." For automation workflows, we need idea + video + thumbnail support via API.

API permissions / scopes

It’d be great to have API permissions or scopes, so that we can create a key with limited powers.Context: We’d like to draft a post or create an idea automatically via GitHub workflow when we merge a community-created pull request. However, because flows may be hijacked (exposing the API key publicly) we need to be sure that the API key cannot be used to directly publish content.

Expose channel groups in Zapier

Would be amazing to have channel groups exposed in Zapier to help minimize task usage.

Binary file upload (FILE_UPLOAD) support for TikTok in MCP API

Hi! Love what you're building with the API - really impressive work so far.Currently, the MCP API only supports URL-based video transfer (PULL_FROM_URL) for TikTok posts. This requires the hosting domain to be verified in TikTok's Developer Dashboard, which creates friction for users hosting videos on third-party services.Adding support for binary file upload (FILE_UPLOAD method from TikTok's Content Posting API) would eliminate the domain verification dependency entirely and allow users to pass video files directly - making TikTok publishing more reliable and flexible.

TikTok support for our API

Expose Post Engagement Metrics via the API

The Buffer GraphQL API currently supports creating and retrieving posts, but the Post type and platform-specific metadata types LinkedInPostMetadata, MastodonPostMetadata, BlueskyPostMetadata) do not include engagement metrics. We're requesting that engagement/analytics data be added to the API so we can programmatically retrieve post performance without scraping the Buffer UI.What we needPer-post engagement metrics for each platform:- LinkedIn: reactions, comments, impressions, reach, engagement rate- Mastodon: favorites, replies, reblogs- Bluesky: likes, comments, repostsIdeally these...

scheduling_type not persisted in MongoDB due to missing Mongoose schema field

scheduling_type is defined on the BaseUpdate TypeScript interface but is not declared in the Mongoose schema. Due to Mongoose strict mode, the field is silently stripped on save, causing the GraphQL API to always return schedulingType: null.

Pinterest post metadata URL field is ignored when creating posts via API

When creating a Pinterest post via the GraphQL API, the url field in PinterestPostMetadataInput is accepted but not persisted. The destination URL for the pin is silently dropped, meaning pins created via the API have no click-through link.

Duplicate post detection blocks new post creation via API after original drafts deleted

Buffer’s duplicate post detection continues to block new post creation via API even after the original drafts that triggered the detection have been deleted. This prevents users from creating posts with the same content after cleaning up drafts.

Instagram Reel update_type inconsistency: 'reel' vs 'reels' mismatch between GraphQL API and legacy code

There’s an inconsistency between how the GraphQL API stores Instagram Reel posts and how legacy code reads them. New posts created via GraphQL API have the post_type as “reel” whereas posts created natively see it stored as “reels.” This causes the reel radio button to not be selected when editing API-created posts.

Instagram firstComment field not persisted when creating posts via API

When creating Instagram posts via the Buffer API with the firstComment field in the metadata, the value is silently ignored and not persisted. This works correctly for Facebook and LinkedIn, but Instagram firstComment returns null and is not saved.Expected: firstComment should be persisted when creating Instagram posts via API, and the response should return the saved value.

Cloudflare restrictions

It would be great if I could get my API to work which is on a VPS and currently hitting Cloudflare restrictions.

Support for addToQueue as Share Mode

API integration with n8n

An API integration directly with n8n with the possibility to post contents would be the best feature !

Buffer MCP - API

It would be great if buffer had an MCP (Model Context Protocol) server where LLM’s could use it to add things to the calendar or use Buffer as a service. I’ve started an AI company and my proof of concept while trying to raise capital is an AI-native consulting company. It would be great if i could add the buffer MCP and use the tools either through my application I’m building, and/or Claude desktop. There are so many people who would benefit from this. Check out Buildship.com and their MCP builder Buildship.tools as well. You could literally build this in a little no time if the api...