Buffer API
★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Publishingoauth218 EndpointsREST
For Agents
Schedule and publish posts across multiple social media profiles, manage content queues, and retrieve posting analytics. Covers 18 endpoints for unified social media management.
Use for: I need to schedule a post to multiple social media accounts, Retrieve all pending posts in a profile's queue, I want to check how many times a URL has been shared through Buffer, List all connected social media profiles for the authenticated user
Not supported: Does not handle social listening, audience analytics, or direct messaging — use for content scheduling, queue management, and share tracking only.
Schedule, publish, and manage social media posts across multiple profiles from a single API with 18 endpoints. Queue content updates with specific scheduling times, reorder and shuffle post queues, track sent post analytics, and retrieve per-profile scheduling configurations. Supports posting to Twitter, Facebook, LinkedIn, and other connected social accounts through a unified content management interface.
Install Jentic One Beta
Connect the Buffer API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buffer API, 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.
1
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 | sh2
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 instanceJentic 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 Buffer API.
Schedule posts to multiple social media profiles with custom publish times
Retrieve pending and sent update queues for each connected profile
Reorder and shuffle queued posts to optimize publishing sequence
Track link sharing statistics across the platform via share count lookups
Fetch per-profile schedule configurations including posting time slots
Move high-priority updates to the top of the publishing queue
Deauthorize user sessions for secure credential lifecycle management
Use Cases
Patterns agents use Buffer API for, with concrete tasks.
★ AI Agent Content Scheduling
An AI agent generates social media content and queues it for publishing across connected profiles by calling POST /updates/create with profile_ids, text content, and optional scheduled_at timestamps. Through Jentic, the agent discovers the scheduling operation by searching 'schedule social media post', loads the request schema with supported fields, and executes without manual API key management. Handles multi-profile posting in a single request.
Create a scheduled post via POST /updates/create with text 'Check out our latest blog post!' targeting profile_ids ['abc123', 'def456'] and scheduled_at set to tomorrow at 9:00 AM UTC
Queue Management and Optimization
Retrieve pending posts for a profile via GET /profiles/{id}/updates/pending, then reorder them by priority using POST /profiles/{id}/updates/reorder or move individual posts to the top with POST /updates/{id}/move_to_top. Shuffle the entire queue randomly using POST /profiles/{id}/updates/shuffle for content variety. Supports queue manipulation without recreating posts.
Retrieve all pending updates for profile-id 'abc123' via GET /profiles/abc123/updates/pending and move update-id 'upd789' to the top via POST /updates/upd789/move_to_top
Multi-Profile Publishing Analytics
Fetch sent post histories for each connected profile via GET /profiles/{id}/updates/sent with pagination to analyze publishing patterns and engagement. Retrieve profile-level schedule configurations showing posting time slots via GET /profiles/{id}/schedules. Compare performance across Twitter, Facebook, and LinkedIn profiles from a unified data source.
Retrieve the last 25 sent updates for profile-id 'abc123' via GET /profiles/abc123/updates/sent?count=25 and return the text and statistics for each
Link Share Intelligence
Look up how many times a specific URL has been shared across the Buffer network using GET /links/shares with the url parameter. Provides aggregate share count data for content performance assessment and viral potential analysis before scheduling reposts or follow-up content.
Check how many times 'https://example.com/blog-post' has been shared via GET /links/shares?url=https://example.com/blog-post and return the shares count
Key Endpoints
18 endpoints — schedule, publish, and manage social media posts across multiple profiles from a single api with 18 endpoints.
METHOD
PATH
DESCRIPTION
POST
/updates/create
Create and schedule a new update
GET
/profiles/{id}/updates/pending
List pending updates for a profile
GET
/profiles/{id}/updates/sent
List sent updates for a profile
GET
/profiles
List all connected social profiles
POST
/updates/{id}/move_to_top
Move an update to top of queue
POST
/profiles/{id}/updates/reorder
Reorder updates in queue
GET
/links/shares
Get share count for a URL
GET
/user
Get authenticated user information
POST
/updates/create
Create and schedule a new update
GET
/profiles/{id}/updates/pending
List pending updates for a profile
GET
/profiles/{id}/updates/sent
List sent updates for a profile
GET
/profiles
List all connected social profiles
POST
/updates/{id}/move_to_top
Move an update to top of queue
POST
/profiles/{id}/updates/reorder
Reorder updates in queue
GET
/links/shares
Get share count for a URL
GET
/user
Get authenticated user information
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Buffer OAuth 2.0 access tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive tokens with posting permissions — raw client secrets and authorization codes never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'schedule a social media post') and Jentic returns the matching POST /updates/create operation with its full request schema including profile_ids, text, and scheduling fields, so the agent can queue content without browsing Buffer's docs.
Time to first call
Direct Buffer API integration: 1-3 days for OAuth setup, profile connection, and queue management logic. Through Jentic: under 1 hour — search for the operation, load the schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Buffer API through Jentic.
What authentication does the Buffer API use?
The Buffer API uses OAuth 2.0 authorization code flow. After authorization, you receive an access_token that must be included as a query parameter or in the Authorization header for all requests. Tokens do not expire but can be revoked via POST /user/deauthorize. Through Jentic, OAuth tokens are stored encrypted in the MAXsystem vault — agents receive scoped tokens without handling raw client secrets.
Can I schedule posts to multiple social media platforms at once?
Yes. Use POST /updates/create with an array of profile_ids to schedule the same content to multiple connected profiles (Twitter, Facebook, LinkedIn, etc.) in a single request. Each profile publishes independently according to its configured schedule or the specified scheduled_at timestamp.
What are the rate limits for the Buffer API?
The Buffer API enforces rate limits per access token. Standard limits allow approximately 60 requests per minute across all endpoints. The POST /updates/create endpoint has additional per-profile limits of 100 queued updates maximum. Rate limit headers are not explicitly documented, so monitor for 429 status codes.
How do I schedule a social media post through Jentic?
Install the Jentic SDK with pip install jentic, then search for 'schedule a social media post'. Jentic returns the POST /updates/create operation with the full request schema showing required text, profile_ids array, and optional scheduled_at, media, and shorten fields. Load the schema and execute with your content. Sign up at https://app.jentic.com/sign-up.
Can I manage the order of queued posts?
Yes. Three queue manipulation endpoints are available: POST /profiles/{id}/updates/reorder lets you specify a complete ordering of update IDs, POST /updates/{id}/move_to_top moves a single update to publish next, and POST /profiles/{id}/updates/shuffle randomizes the entire queue order.
Does the Buffer API provide posting analytics?
Yes. GET /profiles/{id}/updates/sent returns all published posts with their engagement statistics. Each sent update includes retweets, favorites, clicks, reach, and other platform-specific metrics. Use GET /links/shares to check how many times a specific URL has been shared across the Buffer network.
GET STARTED