Changelog
Changes to Tebar's REST API, MCP, and webhooks, newest first.
Nothing here breaks a working integration:
- The API is versioned in the path (
/v1). A breaking change only ships as a new path or field, and the old one keeps working. - New response fields and new optional request fields can appear at any time. Make sure your code ignores fields it doesn't know.
- If you need to change something in your integration, the entry is labeled Action required.
New dashboard features and new platforms are announced at tebar.app/en/changelog.
October 29, 2026
Like Facebook Page and TikTok comments
POST /v1/comments/{id}/like likes a comment as the account. Send { "liked": false } to take it back. In MCP, the tool is like_comment.
Comments now have two new fields:
can_like:trueon Facebook Pages and TikTok. Other platforms answer422 comment_like_unsupported.is_liked: likes made through Tebar. Likes made in the platform's app aren't read back.
curl -X POST https://api.tebar.app/v1/comments/$COMMENT_ID/like \
-H "Authorization: Bearer $TEBAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "liked": true }'Buttons and quick replies in Instagram DMs
POST /v1/inbox/conversations/{id}/messages takes two new optional fields, one or the other per message:
buttons: 1–3 buttons,web_url(opens a link) orpostback(sends itspayloadback). Text up to 640 characters.quick_replies: 1–13{ title, payload }choices. Shown in the Instagram phone app only.
When a customer taps a postback button or a quick reply, a message comes in with kind postback or quick_reply and a postback: { title, payload } field. The message.received webhook carries the same field. send_dm in MCP takes the same fields.
curl -X POST https://api.tebar.app/v1/inbox/conversations/$CONVERSATION_ID/messages \
-H "Authorization: Bearer $TEBAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "Which size?",
"quick_replies": [
{ "title": "S", "payload": "SIZE_S" },
{ "title": "M", "payload": "SIZE_M" }
]
}'The full guide is in DM inbox & automations.
Inbox and Automations in the API Reference
Every /v1/inbox/* and /v1/automations endpoint is now in the API Reference, with request and response schemas. Their behavior hasn't changed.
OpenAPI spec
GET /v1/openapi.json serves the OpenAPI 3.1 spec, no API key needed. It's built from the same schemas the API validates with. Use it to generate a client, import into Postman, or hand it to an AI agent.
media_urls when creating a post
POST /v1/posts takes media_urls: public photo or video links that Tebar downloads into the media library and attaches. You can combine them with media_ids, up to 20 media in total. This used to be MCP only.
Facebook Pages for everyone
The facebook platform is open to every user: posting, comments, and Page statistics.
Oversized bodies answer 413
A request body over the size limit now gets 413 payload_too_large instead of 500.
Threads posting pace
Tebar starts at most 5 Threads posts a minute per account. The rest wait with error_code publish_paced and go out on their own. A thread counts as one post. This keeps Meta from treating a burst of posts from an AI agent as spam.
October 28, 2026
Automatic public replies to Threads comments
POST /v1/automations now works for Threads accounts with kind: "comment_reply". Put 3–5 texts in actions.public_replies, and Tebar picks one at random, waiting at least 30 seconds.
YouTube for everyone
The youtube platform is open to every user. Set a video thumbnail with options.youtube.cover_media_id. GET /v1/accounts/youtube/upload-quota shows the uploads left today.
October 27, 2026
Pin photos to a board with options.pinterest.board_id. GET and POST /v1/accounts/{id}/pinterest/boards read and create boards.
Image covers for TikTok videos
options.tiktok.cover_media_id uses an image from the media library as the cover. video_cover_timestamp_ms still picks a frame.
TikTok video frame rate checked before posting
Videos outside 23–60 FPS are refused up front with video_frame_rate_unsupported instead of failing on TikTok.
October 26, 2026
Instagram DM automations
/v1/automations creates and manages automatic DMs: comment_to_dm, dm_keyword, story_reply, story_mention, default_reply, and ice_breaker. Messages can carry link buttons and a follow_gate. Their history is at GET /v1/automations/{id}/runs. In MCP: list_automations, create_automation, and update_automation.
message.received and automation.run webhooks
Two new webhook events: a new DM from a customer, and the outcome of an automation that answered a comment.
October 25, 2026
Instagram DM inbox through the API
/v1/inbox/conversations reads conversations and messages, sends text, photos, and videos, and marks conversations done. In MCP: list_conversations, get_conversation, send_dm, and set_conversation_status. Paid plans only.
October 24, 2026
New permission for Threads replies and threads
Replying to and hiding Threads comments, threads, and reply_control now need the threads_manage_replies permission. Threads accounts connected before October 24, 2026 need to be reconnected. Until then, those requests answer 422 permission_missing or 422 option_permission_missing. See Limitations.
October 23, 2026
Discord
The discord platform: post to server channels, up to 2,000 characters and 10 files.
October 21, 2026
Ideas board
/v1/ideas, /v1/idea-columns, and GET /v1/ideas/board manage content ideas. Send idea_id with POST /v1/posts to mark the post as made from that idea.
Every post on an account
GET /v1/accounts/{id}/posts lists an account's posts with their full text and numbers. On Threads, Instagram, and TikTok, it includes posts made in the app too. In MCP: list_posts and get_post.
Telegram
The telegram platform: post to channels and groups through Tebar's bot.
October 20, 2026
Profiles, connect links, and webhooks
- Profiles:
/v1/profileskeeps accounts, posts, and media apart per brand or client. TheTebar-Profileheader limits a request to one profile, and API keys can be locked to one. The dashboard calls them workspaces. - Connect links:
POST /v1/profiles/{id}/connect-linksmakes a link for clients to connect their own accounts. - Webhooks:
/v1/webhookssendspost.published,post.failed,comment.created, and account events, signed with theTebar-Signatureheader.
X
The x platform. Each post is paid from your Tebar balance. Not enough balance answers wallet_insufficient.
October 11, 2026
First release
The /v1 REST API with API keys, and the MCP server at https://api.tebar.app/mcp with OAuth 2.1. Posting and scheduling to Threads and Instagram, and comments.