Profiles

Assign placement to group

Moves a single placement (a Facebook Page, LinkedIn organization, Telegram channel, Google Business location, etc.) into a different profile group, independent of where its parent connection is homed. A placement belongs to exactly one group at a time.

patch/api/profiles/{id}/assign_placement_to_group

Request

  • Base URL
    https://api.postproxy.dev
  • URL
    https://api.postproxy.dev/api/profiles/{id}/assign_placement_to_group
  • Auth
    HTTP bearer

Path parameters

idstring required

Profile ID (the connection that owns the placement)

Query parameters

profile_group_idstring

Profile group context for the request. Optional when the API key is scoped to a profile group (that group is used automatically); with a full-access key, defaults to the first profile group in the account.

Headers

Idempotency-Keystring

Optional idempotency key (up to 255 characters; a UUID is ideal). Retrying a successful write with the same key replays the original response (with an Idempotent-Replay: true header) instead of executing again. Stored responses are kept for 24 hours; only 2xx responses are stored.

Request body

placement_idstring required

Platform-specific placement ID, as returned by List placements.

target_profile_group_idstring required

ID of the profile group to move the placement into. Must be in the same environment (live/sandbox) as your API key.

Response

The moved placement, plus its new group

idstring nullable

Platform-specific placement ID. null for personal profile (LinkedIn).

namestring

Display name of the placement.

avatar_urlstring nullable

Stable Postproxy storage URL of the placement's picture, resized to 256x256 (Facebook Pages). null until it has been mirrored and for networks without one.

metadataobject

Extra per-placement data Postproxy stores. For Google Business this carries the location's place_id (Google Maps Place ID). {} when there's nothing extra.

profile_group_idstring

ID of the profile group the placement now belongs to.

Changes

No recorded changes to this operation across all 1 revision of this API.