Skip to content

Assign Linkedin Account To Team

POST
/teams/{team_id}/linkedin-accounts

Attach a LinkedIn sending account to a team.

Two spellings, both accepted because the app accepts both: the current provider + account_ref pair from GET /teams/available/linkedin-accounts, or the legacy linkedin_account_id. Send the pair for new integrations - the legacy id is ambiguous across providers.

Authorizations

Parameters

Path Parameters

team_id
required

Team id (UUID).

string

Team id (UUID).

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

Attach a LinkedIn sending account. Mirrors teams.AssignLinkedInAccountDTO.

All three fields are optional because two spellings are supported: the current provider + account_ref pair, and the legacy linkedin_account_id. The handler validates that one of them is usable.

object
account_ref
Any of:
string
linkedin_account_id
Any of:
string format: uuid
provider
Any of:
string

Responses

200

Successful Response

object
data
required

An open envelope for a single role, team, member or account record.

Open on purpose. The app’s own response models on this surface grow with the product - RoleResponse gained rep_limits and manages_role_slugs, TeamResponse gained channel counts and a campaign count - and a pinned mirror would SILENTLY DROP whatever it had not caught up on. A dropped permission in a role read is the worst possible kind of stale: it reads as “they do not have it”.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string