Skip to content

content_channels_bind

Bind a channel to a platform connector by hand.

Tool

content_channels_bind

Bind a channel to a platform connector by hand.

Bind a channel to a platform connector by hand. For manual cases only: an account connected on the Integrations page already has its own channel. The connector must be attached to this product, match the channel's network and have no other channel in this product (connector_not_found, connector_network_mismatch, connector_already_bound otherwise). Clears an existing pause and turns the channel on. Pass deliveryMode "auto" to also switch the channel to automatic publishing; binding alone never does.

Behavior

HTTP
POST /content/channels/:id/bind

Arguments

Name
Type
Required
Description
id
string
•
The channel id returned by content_channels_list.
connectorId
string
•
The platform connector to publish through — the id of a connector attached to this product. It must be attached and of this channel's network, and not already carried by another channel of this product, or the call is refused with connector_not_found, connector_network_mismatch or connector_already_bound. Networks with no publishing connector (instagram, facebook, tiktok, threads, pinterest, bluesky, telegram, LinkedIn company pages) are refused with no_api_provider.
deliveryMode
string
—
Pass auto to make this API publish through the connector. Omit to keep the current mode: binding alone never switches a channel to automatic publishing.

Response

Field
Type
Always
Description
id
string
•
Channel id — pass this to content_publications_schedule.
origin
string
—
integration: the channel appeared by itself from an account connected on the Integrations page. manual: a seeded channel, or one bound by hand.
enabled
boolean
•
Whether this channel is in use. An integration channel is always true. A manual channel is true once someone turns it on with content_channels_update (a new product starts with every manual channel off). Nothing can be scheduled on a channel that is off: content_publications_schedule refuses it with channel_disabled.
network
string
•
Social network: linkedin, x, youtube, instagram, reddit, facebook, tiktok, threads, pinterest, bluesky or telegram.
pausedAt
string
•
ISO-8601 time the connector stopped working, or null when healthy. A paused channel keeps its scheduled publications — they are frozen, not cancelled, and dispatch once it resumes.
createdAt
string
•
ISO-8601 creation time.
updatedAt
string
•
ISO-8601 time of the last change.
connectorId
string
•
Platform connector this channel publishes through, or null for a reminder channel that needs none. An id — this toolkit never holds social credentials; a token is fetched per call and discarded.
displayName
string
•
Human label for the channel.
networkName
string
•
The network as a person names it — LinkedIn, X, YouTube. Use it to label a network; displayName is the account or channel name.
pauseReason
string
•
Why it paused: revoked (access was taken away), expired (the credential ran out), detached (the integration was detached from this product), removed (the integration was deleted), or the provider reason code from a failed publish. Null when healthy.
subjectType
string
•
Who publishes: member (a personal account) or organization (a company page). Phase 1 channels are all member accounts.
capabilities
object
•
What the channel accepts and what it costs: maxTextLength, maxMedia, supportsVideo, supportsLink, costPerPostUsd, costPerLinkPostUsd, dailyPostCeiling, ceilingIsRuntimeData, acceptsCover (whether the cover of an output is set on the network automatically — the YouTube thumbnail) and coverMaxBytes (the largest cover it takes, or null). Read maxTextLength before writing a per-channel text variant.
deliveryMode
string
•
How the post reaches the network: auto (this API publishes it) or reminder (the system prepares it and notifies a person, who publishes by hand). Every seeded channel is reminder.

Try it

Bind a channel to a platform connector by hand.

When to use

Bind a channel to a platform connector by hand. For manual cases only: an account connected on the Integrations page already has its own channel. The connector must be attached to this product, match the channel's network and have no other channel in this product (connector_not_found, connector_network_mismatch, connector_already_bound otherwise). Clears an existing pause and turns the channel on. Pass deliveryMode "auto" to also switch the channel to automatic publishing; binding alone never does.

Example

Ask your agent something like this:

Bind a channel to a platform connector by hand.

The agent will invoke content_channels_bind with these arguments:

{
  "id": "<id>",
  "connectorId": "<connectorId>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select