# 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.

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`, `502` or `503`). 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`).

> **Before Friday:** Publish anything that can't wait before the maintenance starts, and avoid scheduling new posts for 13 to 16 November.

## 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](/changelog/).

## In the app

1. **Sign in** at [app.socialit.com](https://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).
2. **Check your accounts** under **Accounts**. Reconnect any account marked **Needs reconnect**.
3. **Check your schedule** under **Posts**. Retry any post that failed because it was due during the maintenance.
4. **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](/docs/authentication/))
- IDs: every `ws_…`, `pro_…`, `sa_…`, `pst_…`, `med_…` and other ID stays the same ([Objects and IDs](/docs/concepts/objects/))

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_url` while `has_more` is true ([Pagination](/docs/api-reference/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 on `error.code`, and quote `request_id` when you contact us ([Errors](/docs/api-reference/errors/)).
- **Posts have three new statuses** next to `draft`, `scheduled`, `publishing`, `published` and `failed`: `pending_approval`, `partially_published` and `cancelled`.

### 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 |

> **Old field names are ignored, not rejected:** The API drops fields it doesn't know. A post sent with `target_account_ids` and `publish: true` is saved as an empty **draft** and answers `201`, so nothing is published and nothing fails. Rename the fields above before you send posts to the new API, and check the `status` of the post you get back.

When listing posts, `from`, `to`, `status` and `profile_id` keep their names; `unscheduled` is gone (use `status=draft`). See [Publishing](/docs/publishing/) for everything a post can do now.

### Endpoints that moved

**Accounts**

- `GET /v1/social-accounts` → `GET /v1/accounts`
- `GET`, `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-groups`
- `GET`, `PATCH`, `DELETE /v1/groups/{id}` → same methods on `/v1/account-groups/{id}`
- `GET /v1/groups/{id}/members` → `account_ids` in `GET /v1/account-groups/{id}`
- `POST /v1/groups/{id}/members` → `POST /v1/account-groups/{id}/accounts`
- `DELETE /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/postings`
- `GET /v1/social-postings/{id}` → `GET /v1/postings/{id}`
- `GET /v1/posts/{id}/social-postings` → `GET /v1/postings?post_id={id}`, or `postings` in `GET /v1/posts/{id}`

**Media**

- `POST /v1/media/upload` → `POST /v1/media/upload-direct`: multipart with a `file` field. For large files use `POST /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}/comments`
- `DELETE /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}/hide`
- `POST`, `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/conversations`
- `GET /v1/conversations/{id}` → `GET /v1/inbox/conversations/{id}`
- `GET`, `POST /v1/conversations/{id}/messages` → `GET`, `POST /v1/inbox/conversations/{id}/messages`
- `POST /v1/conversations/{id}/typing` → `POST /v1/inbox/conversations/{id}/typing`
- `POST`, `DELETE /v1/messages/{id}/reactions` → `POST`, `DELETE /v1/inbox/conversations/{conversation_id}/messages/{id}/reactions`

**Reviews**

- `GET /v1/reviews` → `GET /v1/inbox/reviews`
- `POST`, `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-data` and `POST /v1/connect/select` ([Connecting accounts](/docs/connecting-accounts/))

**Validation**

- `POST /v1/validate/post` → `POST /v1/tools/validate/post`
- `POST /v1/validate/post-length` → `POST /v1/tools/validate/post-length`
- `POST /v1/validate/media` → `POST /v1/tools/validate/media`
- `POST /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](/docs/api-reference/idempotency/)).
- **Webhooks** with signed events, instead of polling ([Webhooks](/docs/webhooks/)).
- **OAuth 2.1** for apps that act for other Socialit users ([Authentication](/docs/authentication/)).
- **MCP server** at `https://api.socialit.com/mcp`: every operation as a tool for Claude, Cursor or ChatGPT ([MCP server](/docs/mcp/)).

> **Let an agent do it:** Point Claude, Cursor or another MCP client at this page (`/docs/migrating-to-v1.md`) and your integration's code: the sections above give it every rename.

## Questions

Write to [support@socialit.com](mailto:support@socialit.com) or reply to our email about the move. We read every message.

---

Source: https://socialit.com/docs/migrating-to-v1/
