Guide
Moving to the new Socialit
What changes when Socialit moves to its new platform on 16 November 2026, from the maintenance window to the app, the desktop and mobile apps, and API integrations.
Updated Nov 12, 2026
On Monday, 16 November 2026 Socialit moves to its new platform: a rebuilt app, a new REST API and new desktop and mobile apps. Your workspaces, accounts and posts move over automatically. This page covers the maintenance before the switch, what to do once it’s done, and what to change if you built on the Socialit API.
Maintenance from 13 to 16 November
From Friday, 13 November until Monday, 16 November 2026 Socialit is down while we move every workspace to the new platform.
- The app (web, desktop and mobile) shows a maintenance notice or errors, and you can’t sign in.
- The API answers with errors (
500,502or503). Nothing you send during the window is stored, so pause your jobs or let them retry later. - Scheduled posts move over with everything else. A post that falls due during the window is published once we’re back if it’s at most a day late. An older one is marked as failed (missed schedule), and you can retry it in one click (or with
POST /v1/posts/{id}/retry).
What moves over
Everything moves over automatically. You don’t need to export or import anything.
| Moves over | Notes |
|---|---|
| Your account | Same email and password. |
| Workspaces, profiles and team | Members keep their roles and profile access; pending invitations still work. |
| Connected social accounts | They keep working. Reconnect only the ones marked Needs reconnect. |
| Posts | Published, scheduled and drafts, with their media and per-network results. |
| Media, queues, templates and account groups | Unchanged. |
| Inbox conversations, comments and contacts | Unchanged. |
| API keys | Every sk_live_… key keeps working. |
| Plan and billing | Your plan, limits and payments carry over unchanged. |
Two things don’t move over: sign-ins, so every browser and device signs in once more, and connections or sign-in codes that were still in progress when the maintenance began.
Posting first, more features step by step
The new Socialit starts with Posting: composing, scheduling and publishing to the networks you use today, queues, the media library, templates, profiles and your team. That’s what Socialit did before, now on the new platform.
The new features come next, one at a time:
- when they’re stable, after they’ve run well in production, and
- when the networks approve them: many features need permissions (scopes) that each network reviews before Socialit may use them.
Until a feature is on, the app marks it Soon, and the API answers 403 with the code feature_unavailable. Each new feature is announced in the changelog.
In the app
- Sign in at app.socialit.com with your email and password. If you used to sign in with Google, choose Email me a sign-in code (or Forgot your password? to set one).
- Check your accounts under Accounts. Reconnect any account marked Needs reconnect.
- Check your schedule under Posts. Retry any post that failed because it was due during the maintenance.
- Update your bookmarks. Pages now live under your workspace, for example
app.socialit.com/<workspace>/compose.
The new app also brings two-factor sign-in and passkeys: turn them on under Security in your account settings.
Desktop and mobile apps
The installed Socialit apps keep working with the new platform. Sign in again after the move. A new version of the apps follows shortly after the switch: update when the App Store, Google Play or the macOS app offers it. App Store subscriptions carry over.
API integrations
The base URL, the keys and the IDs stay the same:
- Base URL:
https://api.socialit.com/v1 - Authentication:
Authorization: Bearer sk_live_…with your existing keys (Authentication) - IDs: every
ws_…,pro_…,sa_…,pst_…,med_…and other ID stays the same (Objects and IDs)
The request and response formats changed, and 40 of the 74 endpoints moved. Update your code with the sections below so it’s ready when the new API goes live on 16 November.
Responses
| Before | Now | |
|---|---|---|
| Lists | { "posts": [ … ] } |
{ "object": "list", "data": [ … ] } |
| One object | { "post": { … } } |
The object itself |
| Results per account | targets |
postings |
| Errors | { "error": "NotFound" } |
{ "error": { "type", "code", … } } |
| Post statuses | 5 | 8 |
- Lists are paginated. Before, a list returned everything at once. Now follow
next_page_urlwhilehas_moreis true (Pagination). - Objects come unwrapped, with their type in
object(for example"object": "post"). - Errors share one envelope:
{ "error": { "type", "code", "message", "param", "errors" }, "request_id" }. Branch onerror.code, and quoterequest_idwhen you contact us (Errors). - Posts have three new statuses next to
draft,scheduled,publishing,publishedandfailed:pending_approval,partially_publishedandcancelled.
Creating and updating posts
| Before | Now |
|---|---|
target_account_ids |
account_ids |
config_by_platform |
platform_options |
publish: true |
publish_now: true |
content, media_ids, scheduled_at, queue_id, quote_post_id, strict |
Unchanged |
When listing posts, from, to, status and profile_id keep their names; unscheduled is gone (use status=draft). See Publishing for everything a post can do now.
Endpoints that moved
Accounts
GET /v1/social-accounts→GET /v1/accountsGET,PATCH /v1/social-accounts/{id}→GET,PATCH /v1/accounts/{id}GET /v1/social-accounts/{id}/health→GET /v1/accounts/{id}/health
Account groups
GET,POST /v1/groups→GET,POST /v1/account-groupsGET,PATCH,DELETE /v1/groups/{id}→ same methods on/v1/account-groups/{id}GET /v1/groups/{id}/members→account_idsinGET /v1/account-groups/{id}POST /v1/groups/{id}/members→POST /v1/account-groups/{id}/accountsDELETE /v1/groups/{id}/members/{account_id}→DELETE /v1/account-groups/{id}/accounts/{account_id}
Postings (a post’s result on one account)
GET /v1/social-postings→GET /v1/postingsGET /v1/social-postings/{id}→GET /v1/postings/{id}GET /v1/posts/{id}/social-postings→GET /v1/postings?post_id={id}, orpostingsinGET /v1/posts/{id}
Media
POST /v1/media/upload→POST /v1/media/upload-direct: multipart with afilefield. For large files usePOST /v1/media/presign.
Comments
GET /v1/comments?account_id=→GET /v1/inbox/comments?account_id=GET,POST /v1/comments/{post_id}→GET,POST /v1/inbox/posts/{post_id}/commentsDELETE /v1/comments/{post_id}/{comment_id}→DELETE /v1/inbox/comments/{comment_id}POST /v1/comments/{post_id}/{comment_id}/hide→POST /v1/inbox/comments/{comment_id}/hidePOST,DELETE /v1/comments/{post_id}/{comment_id}/like→POST,DELETE /v1/inbox/comments/{comment_id}/like
Conversations and messages
GET,POST /v1/conversations→GET,POST /v1/inbox/conversationsGET /v1/conversations/{id}→GET /v1/inbox/conversations/{id}GET,POST /v1/conversations/{id}/messages→GET,POST /v1/inbox/conversations/{id}/messagesPOST /v1/conversations/{id}/typing→POST /v1/inbox/conversations/{id}/typingPOST,DELETE /v1/messages/{id}/reactions→POST,DELETE /v1/inbox/conversations/{conversation_id}/messages/{id}/reactions
Reviews
GET /v1/reviews→GET /v1/inbox/reviewsPOST,DELETE /v1/reviews/{id}/reply→POST,DELETE /v1/inbox/reviews/{id}/reply
Connecting accounts
GET,POST /v1/connect/grants/{grant_id}→GET /v1/connect/pending-dataandPOST /v1/connect/select(Connecting accounts)
Validation
POST /v1/validate/post→POST /v1/tools/validate/postPOST /v1/validate/post-length→POST /v1/tools/validate/post-lengthPOST /v1/validate/media→POST /v1/tools/validate/mediaPOST /v1/validate/subreddit→GET /v1/tools/validate/subreddit?name=
Comment and post IDs in the inbox endpoints are the ones those endpoints return. Posts, profiles, queues, media, contacts, custom fields and GET /v1/connect/{platform} keep their paths, with the new formats above.
New in the API
- Idempotency keys on every create and send, so a retry never posts twice (Idempotency).
- Webhooks with signed events, instead of polling (Webhooks).
- OAuth 2.1 for apps that act for other Socialit users (Authentication).
- MCP server at
https://api.socialit.com/mcp: every operation as a tool for Claude, Cursor or ChatGPT (MCP server).
Questions
Write to support@socialit.com or reply to our email about the move. We read every message.