SocialRails
Public APIAPI Changelog

API Changelog

A living changelog of all SocialRails Public API updates, new endpoints, and breaking changes.

All notable changes to the SocialRails Public API are documented here. We follow semantic versioning for the API, and breaking changes will always be announced in advance.

November 2026

New Features

  • Pick the page or board by name over MCP. A new list_destinations tool lists the LinkedIn company pages, Facebook pages and Pinterest boards each connected login can post to. create_post, create_post_batch and update_post take linkedin_pages, facebook_pages and pinterest_board by name, so an assistant can post to the right client page whether clients share one workspace or each have their own. See Choosing pages and boards.
  • Full page and board lists over REST. POST /accounts/{id}/tools with pages, companies or boards now returns every destination the login can post to, with name, id and is_default, instead of only the saved default.
  • Uploads from Dropbox and similar hosts. upload_media_from_url now identifies JPG, PNG, GIF, WebP, MP4 and PDF files from their contents when the host does not label them, and explains when a link opens a web page instead of the file.
  • Connect SocialRails to Claude. A new step-by-step guide for adding SocialRails to the Claude app.

Fixes

  • LinkedIn selectedLocation, Facebook selectedPage and Pinterest selectedBoard given as a plain id (as these docs showed) were not applied: LinkedIn posts went to the personal profile and Facebook and Pinterest posts failed. Plain ids and urn:li:organization: values now work.
  • Setting a single Facebook selectedPage or LinkedIn selectedLocation now replaces a default list of pages instead of being overridden by it.
  • Updating a post's platform_settings or first_comment now keeps its other saved settings. Previously, editing only the first comment cleared the chosen page.
  • LinkedIn page lists now include every page the login can post to, including Content Administrator and Recruiting Poster roles and accounts with more than one page of roles.

No breaking changes.

v1.7.0: Stock photos and multi-workspace keys over MCP

New Features

  • search_stock_photos MCP tool. Assistants can now search free Pexels photos and attach one to a post in the same conversation: search, then upload_media_from_url with the result's image_url, then create_post. Results are sized for posting and include small previews. Requires the read scope. See the MCP Tools Reference.
  • All-workspace API keys. A key created with All my workspaces covers every workspace you own, so one assistant connection can manage all your clients. MCP tools take a workspace argument to pick one, and a new list_workspaces tool lists them. Existing keys are unchanged. See Working across workspaces.
  • Claude app setup guide. MCP Server Setup now covers adding SocialRails as a custom connector in claude.ai, Claude Desktop and the mobile apps.

No breaking changes.

September 2026

v1.6.0: MCP Server

New Features

  • Model Context Protocol support. The API now speaks MCP over Streamable HTTP at POST /api/v1/mcp, so Claude and other AI assistants can work directly in your workspace. Eleven tools cover posts, batch posts, connected accounts, workspace info, media, analytics and AI generation. It authenticates with your existing sr_live_ API keys and enforces the same scopes, plan requirements and hourly rate limits as REST. See MCP Server Setup and the MCP Tools Reference.

No breaking changes. Existing REST integrations are unaffected.

April 2026

v1.5.0: First Comment

New Features

  • First Comment — Automatically post a comment or reply immediately after publishing. Pass first_comment (string, max 2200 chars) when creating or updating posts via POST /api/v1/posts, POST /api/v1/posts/batch, or PATCH /api/v1/posts/:id. Supported on Twitter/X (posts as a reply), LinkedIn (comment on post), Facebook (comment on page post), and Bluesky (reply). Also available in the dashboard UI, n8n node, and CLI.

March 2026

v1.4.0: Threading API, Discovery Endpoints, Platform Settings

New Endpoints

  • GET /api/v1/accounts/:id/settings — Get platform capabilities, character limits, media specs, workspace defaults, and available tools for a connected account.
  • POST /api/v1/accounts/:id/tools — Trigger platform discovery tools (Facebook pages, Pinterest boards, LinkedIn companies, Twitter communities).

New Features

  • Threading API — Create Twitter and Threads reply chains via POST /api/v1/posts using the new thread, thread_media, and thread_delay fields. Supports 2-25 items per thread with per-platform character limits.
  • Platform Settings Documentation — New dedicated Platform Settings Reference documenting all 9 platforms with character limits, media specs, threading support, settings fields, and examples.
  • socialrails CLI — New standalone CLI package on npm for scheduling posts, managing accounts, generating AI content, and viewing analytics from the terminal. JSON output for scripting and AI agent integration.

Improvements

  • OpenAPI spec — Added PlatformCapabilities and PlatformSettings schemas, thread fields on CreatePostRequest.
  • n8n package — Expanded README with installation methods, operations reference, workflow examples, platform notes, and troubleshooting.

v1.3.0: Media Uploads, Batch Posting, Full CRUD

New Endpoints

  • POST /api/v1/posts/batch, Create posts for multiple platforms in a single request. Posts are linked by a batch_id.
  • POST /api/v1/media/upload, Upload images and videos via multipart form data (up to 10MB).
  • POST /api/v1/media/upload-url, Upload media by providing a URL to fetch from.
  • DELETE /api/v1/posts/:id, Delete draft or scheduled posts.
  • PATCH /api/v1/posts/:id, Update content, platform, or schedule for draft/scheduled posts.
  • GET /api/v1/health, Public health check endpoint (no authentication required).

Coming Soon

  • POST /api/v1/webhooks, Register webhook URLs to receive event notifications.
  • GET /api/v1/webhooks, List your registered webhooks.
  • DELETE /api/v1/webhooks/:id, Remove a webhook registration.
  • Webhook event delivery (post.published, post.failed, post.scheduled) will be enabled in a future update. You can already register endpoints via the API.

Improvements

  • Posts list: Added sort, platform, from, and to query parameters for filtering and sorting.
  • Analytics: Added 365d period option and per-post analytics via post_id query parameter.
  • Accounts: Response now includes status field (connected or expired).
  • Workspace: Response now includes usage object with posts_this_month count and full plan limits.
  • Batch posting: New batch_id field links posts created together.
  • Media support: Posts now accept optional media field (array of R2 keys from the upload endpoint).

Infrastructure

  • Router refactored to declarative route table for cleaner endpoint management.
  • CORS now allows DELETE and PATCH methods.
  • Body size limit increased to 10MB for media upload endpoints.

v1.2.0: Initial Public API

  • GET /api/v1/posts, List scheduled posts with pagination
  • GET /api/v1/posts/:id, Get a single post
  • POST /api/v1/posts, Create and schedule posts
  • GET /api/v1/analytics, Aggregate publishing analytics
  • GET /api/v1/accounts, List connected social accounts
  • POST /api/v1/ai/generate, AI content generation
  • GET /api/v1/workspace, Workspace info and plan limits

Versioning Policy

The SocialRails API uses URL-based versioning (/api/v1/). We will:

  • Never remove or rename existing fields in a response without a version bump
  • Always announce breaking changes at least 30 days in advance
  • Add new optional fields to responses without a version bump (additive changes are non-breaking)
Updated 3 days ago
<- API Code Examples
API Authentication ->