In short
A multi-tenant social publishing API needs platform-level credentials, isolated customer profiles, hosted OAuth connect per profile, and posts that report results per network rather than a single all-or-nothing status.
When software publishes for many brands or clients, each end customer needs a stable profile boundary. That profile owns connected accounts and post history so one tenant never acts on another’s pages.
OAuth belongs in a hosted connect flow: your product starts a session, the end user authorizes Facebook, Instagram, or LinkedIn, and tokens stay encrypted on the publishing layer—not in your application database as long-lived raw secrets if you can avoid it.
Publishing should fan out into network legs. One network can fail while others succeed; operators need that truth in the API response and in webhooks.
Social Relay implements this model for Facebook, Instagram, and LinkedIn with prepaid token metering for billable actions.