Start a channel connection
GET /public/v1/social/{integration}Starts connecting a new channel. Sharek generates the platform’s authorization URL and returns it; you send the person there to approve. When they come back, the channel is attached to your organization.
Path parameters
Section titled “Path parameters”| Parameter | Required | Description |
|---|---|---|
integration |
Yes | The provider identifier, for example linkedin, x, youtube. The same values list channels returns as identifier. |
Query parameters
Section titled “Query parameters”| Parameter | Required | Description |
|---|---|---|
refresh |
No | An existing channel id. Use it to reconnect that channel rather than adding a new one. |
Request
Section titled “Request”curl -H "Authorization: your-api-key" \ https://dash.sharek.app/api/public/v1/social/linkedinReconnecting an existing channel:
curl -H "Authorization: your-api-key" \ "https://dash.sharek.app/api/public/v1/social/linkedin?refresh=channel-id"Response
Section titled “Response”{ "url": "https://www.linkedin.com/oauth/v2/authorization?..." }Open that URL in a browser. After approval the platform redirects back to Sharek, which finishes the connection.
Not every channel can be connected this way
Section titled “Not every channel can be connected this way”| Response | Meaning |
|---|---|
400 {"msg": "Integration not allowed"} |
The identifier is not on the offered catalog. Check the spelling against list channels or the connecting channels page. |
400 {"msg": "This integration requires an external URL and is not supported via the public API"} |
The provider needs an instance URL supplied up front, which this operation cannot collect. Connect it in the app instead. |
402 |
The organization has no channel slots left. The body carries a url pointing at where to resolve it. |
500 {"msg": "Failed to generate auth URL"} |
Sharek could not build the platform URL. Retry; if it persists the provider is misconfigured. |
Only channels that redirect work here
Section titled “Only channels that redirect work here”This operation is built for the channels that connect by sending you to the platform’s own sign-in screen. The others connect by collecting credentials in a form or through an in-app dialog, and neither can be driven from an HTTP call.