Bufferapp

Name: Bufferapp API
Brand: Bufferapp
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Publishingoauth218 EndpointsREST

For Agents

Schedule and manage social media posts across connected Buffer profiles, retrieve sent posts and engagement, and edit the publishing queue.

Install Jentic One Beta

Connect the Bufferapp to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bufferapp, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Bufferapp API.

List the social profiles a user has connected to their Buffer account

Create a new pending update and target it at one or more profiles

Edit a pending update's text, media, or scheduled time before it sends

GET STARTED

Start building with Bufferapp API

Explore with Jentic

View OpenAPI Document

Buffer's API schedules, edits, and analyses social media posts across the connected profiles a user has linked to their Buffer account, including Twitter, Facebook, LinkedIn, and Instagram. The spec covers profile listing and schedule management, creation and editing of pending updates, reordering and shuffling the publishing queue, retrieving sent posts and their interactions, and shortening links via /links/shares. It is the standard integration entry point for cross-network scheduling, marketing automations, and content-calendar tools that publish through Buffer.

Use Cases

Patterns agents use Bufferapp API for, with concrete tasks.

★ Cross-Network Content Calendar

Publish a single content calendar across Twitter, LinkedIn, Facebook, and Instagram by listing profiles via /profiles and creating one update per network with /updates/create. Buffer queues each update according to that profile's schedule, so the marketer authors once and Buffer handles per-network timing. End-to-end scheduling for a week of posts moves from per-network manual work to a single API loop.

Call /profiles to list connected profiles, then for each profile call /updates/create with the post text and chosen scheduled_at time

Queue Management Automation

Automate Buffer queue housekeeping by reordering pending updates with /profiles/{id}/updates/reorder, shuffling for variety with /profiles/{id}/updates/shuffle, or pushing a time-sensitive post to the top with /updates/{id}/move_to_top. Useful for marketing teams who plan a week of evergreen content but need to insert breaking announcements without rebuilding the queue.

Call /updates/{id}/move_to_top for the breaking announcement so it ships in the next available slot

Engagement Reporting

Pull sent-post engagement into BI tools by listing /profiles/{id}/updates/sent for a profile and then reading /updates/{id}/interactions for each post. The interaction counts (likes, comments, retweets) feed weekly performance reports without requiring a Buffer Analytics seat. Combined with the link-share data from /links/shares, this measures both engagement and click-through.

Call /profiles/{id}/updates/sent for the last 7 days, then call /updates/{id}/interactions for each ID and aggregate into the report

AI Agent Posting Through Jentic

Allow an AI agent to schedule social posts on a marketer's behalf without holding the Buffer access token. Through Jentic, the agent searches by intent, loads the create-update schema, and executes against /updates/create with the chosen profile_ids and scheduled_at. The OAuth access token is stored in the Jentic vault and injected at execution time so credentials never enter the agent's context.

Use Jentic to search 'schedule a Buffer post', load the create-update schema, and execute against /updates/create with the post text and target profile IDs

Key Endpoints

18 endpoints — buffer's api schedules, edits, and analyses social media posts across the connected profiles a user has linked to their buffer account, including twitter, facebook, linkedin, and instagram.

METHOD

PATH

DESCRIPTION

GET

/profiles

List connected social profiles

POST

/updates/create

Create a new pending update on one or more profiles

GET

/profiles/{id}/updates/pending

List pending updates for a profile

GET

/profiles/{id}/updates/sent

List sent updates for a profile

POST

/updates/{id}/update

Edit a pending update

POST

/updates/{id}/move_to_top

Move an update to the top of the queue

GET

/updates/{id}/interactions

Get interaction counts for a sent update

POST

/profiles/{id}/schedules/update

Update the posting schedule for a profile

GET

/profiles

List connected social profiles

POST

/updates/create

Create a new pending update on one or more profiles

GET

/profiles/{id}/updates/pending

List pending updates for a profile

GET

/profiles/{id}/updates/sent

List sent updates for a profile

POST

/updates/{id}/update

Edit a pending update

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Buffer's OAuth client_id, client_secret, and per-user access tokens are stored encrypted in the Jentic vault. Jentic handles the authorization-code exchange and refresh server-side and injects the access token at execution time so the raw credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'schedule a Buffer post') and Jentic returns the matching create-update operation with its schema, so the agent calls /updates/create without browsing Buffer's developer docs.

Time to first call

Direct Buffer integration: 1-2 days for OAuth handling, profile resolution, and schedule semantics. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Bufferapp API through Jentic.

What authentication does the Buffer API use?

Buffer uses OAuth 2.0 with the authorization code flow. After the user authorises your app, exchange the returned code for an access_token at Buffer's token endpoint. Send the access_token in the HTTP Authorization header, request body, or query string on subsequent calls. Through Jentic the OAuth client secret and access token are stored encrypted in the vault and injected at execution time.

Can I schedule a post with the Buffer API?

Yes. POST to /updates/create with text, profile_ids (an array of one or more profile IDs from /profiles), and either scheduled_at (Unix timestamp) for a specific time or now=true to add to the front of the queue. Buffer queues the update according to the profile's posting schedule and returns the new update ID.

What are the rate limits for the Buffer API?

Buffer applies a rolling per-token limit (historically 60 requests per minute for most endpoints). The exact value is not in this spec — see Buffer's developer docs at buffer.com/developers/api for current limits. The API returns 429 responses when the limit is exceeded and clients should back off before retrying.

How do I list pending posts through Jentic?

Install the SDK with pip install jentic, search for 'list pending Buffer posts', load the relevant schema, and execute it against /profiles/{id}/updates/pending with the profile ID. Jentic injects the OAuth access token from the vault and returns the list of unsent updates with their scheduled times.

Can I edit a Buffer update after creating it?

Yes, while it is still pending. POST /updates/{id}/update with the new text, media, or scheduled time and Buffer replaces the queued update in place. Once a post has been sent (visible via /profiles/{id}/updates/sent) it can no longer be edited via the API.

Is the Buffer API free?

Buffer offers a free plan with limited connected profiles and posts; paid plans (Essentials, Team, and Agency) raise those limits. API access is available across plans and is billed against the same per-account quotas. See buffer.com/pricing for current details.

Bufferapp

Connect the Bufferapp to your agent

Capabilities

Start building with Bufferapp API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs