Skip to content

Move Social Account API: Move between social groups

The Move Social Account API reassigns a connected social account integration to another profile without reconnecting it. It suits handovers between teams, brands, or workspaces: the integration retains its identifier, its OAuth credentials, and posts already published through it, while only its profile assignment changes.

Move between social groups: what changes and what is preserved

Move between social groups when responsibility for a connected account shifts. This operation is a reassignment rather than a fresh connection: the integration identifier stays the same, its OAuth credentials remain attached, and posts already made through it stay linked, so anything referencing that identifier continues to work after the profile changes. Decide first which integration identifier to target and which destination you intend, since one endpoint covers both a named profile and the Default destination via the profileId field.

From the dashboard

For a manual move, open the dashboard, go to Integrations, locate the relevant account, and choose Move. Pick the social group you want as the destination and confirm. Selecting Default instead takes the account out of its current group. This route works well for occasional handovers; the API route below fits repeatable workflows or moves that should be logged with other project changes.

Endpoint and field map

The endpoint is PATCH {{API_BASE_URL}}/v1/connect/integrations/{id}. In the path, id is a string holding the integration identifier, which you can obtain from the List endpoint. In the body, profileId is typed string | null: supply a destination profile identifier as a string for a named profile, or supply null for Default. Eligibility matters here — the target needs to be active, and it must sit within the same project as the integration. If either condition is unmet, fix the profile state or project membership before trying again.

Move to another social group

For a named destination, set profileId to that profile's identifier — profile_acme in the examples below — and call PATCH for integration abc123, as shown in the Move to another social group examples. After a successful call, inspect the returned integration object: profileId should show the destination you requested, while id, platform, username, authStatus, and createdAt describe the same integration. If profileId does not match your request, regard the move as unconfirmed and investigate rather than assuming the account now sits in the destination profile.

Move to Default

To Move to Default, send the same PATCH request with profileId set to null, as shown in the Move to Default example. This suits situations where the account should leave its current group but not yet join a named profile. Use null for the Default destination, as specified by the contract, rather than a string profile identifier.

Response shape and preserved integration fields

On success, the response carries success set to true alongside the updated integration object, as shown in the Response example. Treat that returned object as your confirmation of the new assignment, not merely the request you sent. Check that the integration id matches the account you meant to move and that profileId matches the destination — or is null for Default — before updating your own records or telling stakeholders the reassignment is done.

Destination conflicts and failure checks

Destination conflicts arise because each profile within a project may hold only a single copy of a given social account. When the destination already holds that account, the API responds with 409. Resolve it by picking a different profile, or by disconnecting the duplicate integration first, then retry. Repeating the identical request against the same destination will not resolve it. For other failures, consult the failure matrix below: 400 signals an invalid profileId or request body, while 404 signals that the integration or destination profile could not be found, so verify the integration identifier from List and the destination profile identifier before resending.

Field map for id and profileId
LocationParameterTypeDescription
PathidstringIntegration ID from the List endpoint
BodyprofileIdstring | nullDestination profile ID. Pass null to move the integration to Default. Target must be active and in the same project as the integration.

Exact contract fields preserved; origin modularized as {{API_BASE_URL}}.

Named profile versus Default decision criteria
Destination choiceprofileId valueUse whenEffect
Named social groupstring, for example profile_acmeThe account should belong to a specific active profile in the same projectIntegration is reassigned to that profile
DefaultnullThe account should leave its current social group without joining a named profileIntegration is moved to Default

Decision criteria derived from the captured source contract; no new endpoint behavior introduced.

Failure matrix for move requests
Status codeMeaningLikely causeNext action
200Integration movedRequest succeededConfirm the returned integration profileId and update your records
400Invalid profileId or request bodyMalformed body or invalid profileId valueCorrect the body and profileId, then retry
404Integration or destination profile not foundWrong integration id or destination profile idRe-check the integration ID from List and the destination profile ID
409The social account already exists in the destination profileDestination conflicts: the same social account is already present in that profileChoose another profile or disconnect the duplicate integration before retrying

Status meanings preserved exactly; cause and next action are explanatory guidance only.

Frequently asked questions

How do I move a social account to another profile?

Send PATCH {{API_BASE_URL}}/v1/connect/integrations/{id} with profileId set to the destination profile ID. The destination must be active and belong to the same project as the integration.

How do I move an integration to Default?

Send the same PATCH request with profileId set to null. That removes the account from its current social group and moves it to Default.

What does a 409 destination conflict mean?

The API returns 409 when the destination profile already contains the same social account. Choose another profile or disconnect the duplicate integration before retrying.

Does moving an account require reconnecting it?

The integration keeps its ID, OAuth credentials, and existing posts. You do not need to reconnect the account to move it between profiles.

Endpoint
PATCH {{API_BASE_URL}}/v1/connect/integrations/{id}
Move to another social group with cURL
curl -X PATCH "{{API_BASE_URL}}/v1/connect/integrations/abc123" \
  -H "x-access-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "profileId": "profile_acme" }'
Move to Default with cURL
curl -X PATCH "{{API_BASE_URL}}/v1/connect/integrations/abc123" \
  -H "x-access-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "profileId": null }'
Response example
{
	"success": true,
	"integration": {
		"id": "abc123",
		"platform": "twitter",
		"username": "@example",
		"profileId": "profile_acme",
		"authStatus": "active",
		"createdAt": "2026-03-28T10:00:00.000Z"
	}
}