Bufferapp

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.

Can I limit what my agent is allowed to do with the Buffer API?

Yes. Because you run your own self-hosted Jentic One instance, your own rules decide which Buffer operations and credentials the agent may use, and the operator sets those limits. Since Buffer puts the profile id in the URL path (/profiles/{id}/updates/...), a rule can pin the agent to a single profile so it can create and edit updates with /updates/create and /updates/{id}/update and adjust that profile's schedule and nothing else. You choose the allowed operations, so the agent can schedule and edit posts without being able to reorder the queue or call /updates/{id}/move_to_top unless you grant those. The OAuth access token stays with your instance and is injected at execution time, so it never enters the agent's context.