Use casesMulti-tenant

Social publishing for every customer of your product

If your product posts to social media on behalf of its users, you need isolation, an easy way for each user to connect their accounts, and a bill that does not grow with every account. Siar is built around that.

  • A team per customer, brand or location, with at most one account per network.
  • Unlimited teams (and so accounts) on paid plans; 3 teams on Free.
  • Hosted connect pages for your users, with your logo and name.
  • Every query is scoped to your organization; ids from elsewhere return 404.

Teams are your tenants

Create a team when a customer signs up and store its id against your own user record. Every upload, post, comment and connected account lives under a team, so listing a customer's posts is one query with their teamId.

curl -X POST "https://api.siaran.my/api/v1/team" \
  -H "x-api-key: $SIAR_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "name": "Acme Bakery" }'
# → { "id": "TEAM_ID", "name": "Acme Bakery", ... }

Customers connect their own accounts

Send each customer a hosted connect link, or call the connect endpoint from your own settings page. They sign in with the network, and the account appears in their team. Siar notices when a network revokes access and fires a social-account.updated webhook so you can prompt a reconnect.

Pricing that follows usage

Quotas count what your organization creates each month. Adding a customer, or a customer adding an Instagram account, costs nothing until they actually publish. Daily caps per account protect each customer's accounts from being throttled by the networks.

Works with every supported network

Frequently asked questions

Can one team connect two Instagram accounts?

No. A team holds at most one account per network. Create a second team for the second account.

Can I give customers their own API keys?

API keys belong to the organization. Keep them on your server and call Siar on behalf of the customer's team. Customer-facing connect pages use short-lived portal tokens, not your key.

Is data from one customer visible to another?

Queries are scoped to your organization, and within it to the team you name. Foreign ids return 404 rather than 403, so ids cannot be probed.

Keep reading

Your first post isone request away.

The Free plan includes 20 posts and 200 uploads a month across 3 teams. No card needed.