Answers about Social Relay’s multi-tenant social API.
Plain-language answers on what Social Relay is, who it serves, supported networks and account types (Facebook Pages, Instagram professional, LinkedIn personal only, Bluesky, Mastodon), profiles, publish legs, prepaid tokens, and where the API is hosted—structured for humans and answer engines.
What is Social Relay?
Social Relay is a multi-tenant social publishing API. Software platforms use it to connect Facebook, Instagram, and LinkedIn for each of their customers and to publish through one REST API with prepaid token billing.
Who is Social Relay for?
Social Relay is for product teams embedding social publishing in SaaS, and for operators or agencies that manage professional social accounts through an API. End customers authorize network accounts via hosted connect; your product owns the UX. It is not a standalone consumer social app.
Which social networks does Social Relay support?
Launch networks and account types: Facebook Pages only (not personal Facebook profiles); Instagram Business or Creator accounts linked to a Facebook Page; LinkedIn personal (member) profiles only (not Company Pages); Bluesky (handle + app password); and Mastodon (instance OAuth). Additional networks may be added later.
How does Social Relay billing work?
Usage is metered with prepaid tokens. Billable actions include validation, listing, connect, publish legs, and webhooks according to the published rate card. Token balance lives on the platform account.
What is a profile?
A profile is one end customer, brand, or location under a platform account. Connections and posts are scoped to that profile so multi-tenant isolation is enforced by the API.
What is a publish leg?
Each target network on a post is a leg. Legs can succeed or fail independently, so a post can be partially successful when one network errors.
Where is the API hosted?
The public API base is https://api.socialrelay.dev. Marketing and documentation live at https://socialrelay.dev. Machine-readable OpenAPI is at /api/v1/openapi.json on the API host.
How do end users connect social accounts?
Your backend creates a hosted connect session for a profile and redirects the user to the returned connect URL. They complete OAuth (or sandbox) and return to your success or cancel URL.
What is the Social Relay rate card?
The rate card lists prepaid token costs per API action (validate, list, connect, publish legs, retry, media validate, webhooks). It is versioned and available via GET /api/v1/rate-card and on the Pricing page.
How do I verify Social Relay webhooks?
Verify the X-Social-Restapi-Signature header. The value is t=<unix>,v1=<hex> where v1 is HMAC-SHA256 of the string `{t}.{raw_body}` using your webhook secret.
Does the dashboard use API keys in the browser?
No. The platform dashboard uses email/password sessions (optional TOTP). Platform API keys are for server-side product traffic only.