Skip to main content
POST
/
social_accounts
Connect a Social Account
curl --request POST \
  --url https://{defaultHost}/social_accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "redirect_url": "<string>",
  "platform": "meta_business",
  "scopes": [
    "advertise"
  ]
}
'
{
  "authorize_url": "<string>"
}

Authorizations

​
Authorization
string
header
required

An account API key, account scoped JWT, app API key, or user OAuth token.

Headers

​
Api-Version-Date
string<date>

Pins the request to a dated API version. When omitted, the request uses the original (2025-01-01) request/response shapes, so existing unversioned callers are never broken. Generated SDKs always send the latest version they were built against. An unrecognized value is rejected with a 400. The schemas documented here always describe the latest version.

Example:

"2026-06-09"

Body

application/json
​
redirect_url
string
required

The Whop URL to redirect the user to after they finish connecting.

​
platform
enum<string>
required

The platform to connect the social account on.

Available options:
meta_business
​
scopes
enum<string>[]

Capabilities to grant for the connected social account, for example advertise.

Available options:
advertise

Response

authorize url returned

​
authorize_url
string
required

The OAuth authorization URL to redirect the user to.