# How to add social media publishing to your SaaS without going through app review

Sooner or later, the users of a content generator, a CRM or a tool for small businesses all ask for the same thing: "can I post this straight to Instagram?". On the roadmap it looks like a small task: one button and one API call.

It isn't. This guide explains what's behind it, why the hard part isn't the code, and how the wyro API partner API handles it. It also says what it doesn't handle.

## What building it directly involves

To post on your users' behalf on a social network, your product needs a developer app approved by that network. For each one, that means:

- **Creating the app and requesting publishing permissions.** On Meta (Instagram, Facebook and Threads), TikTok, LinkedIn, Google (YouTube), X and Pinterest. That's eight networks and six different processes.
- **Passing review.** Every network asks for something similar: explain what you use each permission for, record a video of your product using it, publish a privacy policy and, in several cases, verify your business. Until the app is approved, it only works with test accounts or with restrictions: TikTok, for example, keeps videos from unaudited apps private.
- **Waiting.** Timelines vary, they don't depend on you, and a rejection sends you back to the start.

Then the real work begins, which is maintaining it:

- Tokens that expire and need refreshing, different on every network.
- API versions that get retired and permission changes that force you to update.
- Each network's own format rules: text length, mandatory video on TikTok and YouTube, carousels, stories.
- Errors that every network reports its own way.

If your product only needs one network and you have time for its review, integrating directly makes sense: you don't depend on anyone. The problem shows up when your users want three, five or eight networks.

## The alternative: an API whose app is already approved

A publishing API like wyro API has already been through those reviews. Your users authorize the connection through that approved app, so your product doesn't need to register its own on each network or go through any app review. You talk to a single API for all eight networks: Instagram, Facebook, TikTok, LinkedIn, X, Threads, YouTube and Pinterest.

It's worth being clear about what that means, because it isn't magic:

- **Your users never create a wyro API account.** But this isn't full white label: the connect link goes through the wyro API domain, and the network's consent screen shows the name of the approved app that makes the connection, not your product's name. Before and after that step, everything happens in your UI.
- **You depend on a provider.** If something changes on a network tomorrow, we deal with it, but your publishing depends on our API being up.
- **Posts go through the official APIs.** No browser automation and no stored passwords.

## What the flow looks like in your product

The partner API has four steps. All of them run from your backend.

### 1. One workspace per customer

Each of your customers is a workspace with its own key and its own connected accounts. You create it with your partner token:

```bash
curl -X POST https://wyroapi.com/v1/partner/workspaces \
  -H "Authorization: Bearer $PARTNER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"external_id":"customer-123","webhook_url":"https://api.your-saas.com/webhooks/wyro"}'
```

`external_id` is the customer's id in your system, and the call is idempotent: if you repeat it, you get the same workspace back. The first response includes the workspace's `api_key` and the `webhook_secret`; store them encrypted, because they're never shown again. A workspace's key only sees that workspace's accounts: an `account_id` from another one returns 404.

### 2. A connect link

When the user clicks "Connect Instagram" in your product, you ask for a link with their workspace's key:

```bash
curl -X POST https://wyroapi.com/v1/connect \
  -H "Authorization: Bearer $WORKSPACE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"platform":"instagram","return_url":"https://app.your-saas.com/social/connected"}'
```

The response includes a signed `connect_url` that expires in 24 hours. It can't be altered to point at another workspace or another network, and `return_url` has to be https.

### 3. The user authorizes and comes back

Your user opens the link, goes straight to the network's official authorization, with no wyro API login, and comes back to your `return_url` with the result in the query string:

- `wyro_status=connected`, with `account_id`, `platform` and `username`, or
- `wyro_status=error`, with the reason in `reason` (for example, `cancelled` if they changed their mind).

You store the `account_id` next to the customer. To confirm it server-side, `GET /v1/accounts` lists the workspace's accounts, and you also get the `account.connected` event.

### 4. Publish with account_ids

```bash
curl -X POST https://wyroapi.com/v1/posts \
  -H "Authorization: Bearer $WORKSPACE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"New launch","account_ids":["acc_..."],"media":[{"url":"https://your-saas.com/img/launch.jpg"}],"scheduled_at":"2026-12-01T10:00:00-05:00"}'
```

Without `scheduled_at`, the post goes out right away. The same call works for any of the eight networks.

## Details worth designing from day one

**Webhooks, not polling.** Your `webhook_url` receives `post.published`, `post.partial` and `post.failed` when a post reaches its final status, with the published link or the error for each network, plus `account.connected` and `account.disconnected`. Every delivery is signed (`X-Wyro-Signature`, an HMAC-SHA256 of `<timestamp>.<body>` with your `webhook_secret`): verify it and reject timestamps older than 5 minutes. Today each event is delivered with two attempts and no later retries, so respond quickly with a 2xx, process in the background and, if a status is critical, confirm it with `GET /v1/posts/{id}`.

**Disconnections.** If a user revokes access from the network, you get `account.disconnected`, the account becomes `disconnected` and publishing to it returns `account_disconnected`. The sensible move is to show a "Reconnect" button that asks for a new link.

**Validation before publishing.** Each network has its limits: 2,200 characters on Instagram, 280 on X, mandatory video on TikTok and YouTube. The API validates the same rules, and every error comes with a code, the reason and how to fix it, in English, Spanish or Portuguese, so you can show it to your user.

**Keys stay in the backend.** The partner token and the workspace keys never go to the browser. `POST /v1/partner/workspaces/{id}/key` rotates a key instantly, and `DELETE /v1/partner/workspaces/{id}` offboards a customer: it disconnects their accounts and revokes the key.

## What it doesn't do yet

So you don't find out halfway through the integration: today wyro API publishes and schedules, but it doesn't provide post metrics (insights), ads or automated direct messages.

## Pricing and how to get started

The public price is USD 5 per connected account per month, with no per-seat or per-post charge. If your users will connect a lot of accounts, volume terms are something we talk through. The partner token isn't generated from the dashboard: we enable it after a short call, which you can request from [the SaaS page](https://wyroapi.com/en/for-saas).

Meanwhile, you can try publishing for free, with no sign-up, using a sandbox key with simulated accounts on all eight networks.

More: [Docs: getting started](https://wyroapi.com/en/docs/getting-started) · [Accounts and connection](https://wyroapi.com/en/docs/accounts) · [Partner API for agencies and SaaS](https://wyroapi.com/en/blog/white-label-social-media-api-for-agencies) · [Post without Meta or TikTok approvals](https://wyroapi.com/en/no-app-review).

---
Published on 2026-11-17 at https://wyroapi.com/en/blog/add-social-media-publishing-to-your-saas
