Log inStart Free Trial
easyCoexistence Official APIs

Unified social media API for SaaS: one integration for WhatsApp, Instagram, Facebook, TikTok, YouTube, LinkedIn and more channels

easyCoexistence's Partner API gives a SaaS one integration for its customers' WhatsApp, Instagram, Facebook, TikTok, YouTube, LinkedIn and more channels. One API key and one connect-session call connect them; the same calls list them, return fresh credentials, set webhooks and send signed status events, and one posts endpoint publishes to Instagram, Facebook, TikTok and LinkedIn. Replies go through each network's own API with the customer's token.

1 key

Partner API keys per easyCoexistence account; every number and social account it connects belongs to that account.

US$ 9 to US$ 0.75

Monthly price per connection, the same for a WhatsApp number and a social account, falling as the count grows.

100 posts

API-published posts an Instagram account can make in a moving 24 hours; a carousel counts as one.

15 a day

Video posts TikTok publishes per account through its API, at no more than six a minute.

24 hours

WhatsApp's customer service window after a user's message; once it closes, only approved templates can be sent.

What does one integration cover?

The work that is the same across networks, from https://easycoexistence.com/api/v1 with one ec_live_ key. Your code learns these calls once, and a customer's TikTok account is handled the way their Instagram account is, with the same errors, the same IDs and the same signed events:

ConnectPOST /connect-sessions, with channel set to the network
ListGET /connections for numbers, GET /channels for social accounts
Credentials?credentials=1 on either, with tokens renewed for you
WebhooksPUT /connections/{id}/webhook or PUT /channels/{id}/webhook
Status eventsconnection.* and channel.*, signed, with your external_ref
PostsPOST /channels/{id}/posts, now or at publish_at
RemoveDELETE on the connection or the channel

What does each network still decide?

What its API allows. easyCoexistence connects, renews and watches each account the same way, while the features your product can offer follow each network's own rules, so DMs, comment events and post types differ from one network to the next:

WhatsAppMessages and replies on the Cloud API, templates outside the 24-hour window
InstagramPosts, carousels, Reels and Stories; comments; replies to DMs
FacebookPage posts; comments; replies to Messenger DMs
TikTokVideo and photo posts; public replies to comments; no DMs
YouTubeUploads and comments through YouTube's own API; no DMs
LinkedInPosts a person approves, text with an image or a link; no DMs

Why are numbers and social accounts separate resources?

Because they hold different things. A number has a phone, a WhatsApp Business Account and Meta's ratings; a social account has a handle and a network ID. So numbers live at /connections and social accounts at /channels, each with its own IDs, its own redirect parameter, connection_id or channel_id, and its own event names. A WhatsApp-only integration never meets a channel unless it asks for one, and connecting is the one call they share.

How does one posts call work across networks?

The body is the same everywhere: text, media, link and publish_at, plus a few fields one network reads, such as ig_type on Instagram, title and disable_comment on TikTok and image_alt on LinkedIn. Each network's limits are checked before the post is queued:

  • Instagram: one image or video, or a carousel of 2 to 10; JPEG images; no link field; text up to 2,200 characters.
  • Facebook: text, a link, one image or one video; text up to 63,206 characters.
  • TikTok: one video, or a photo post of 1 to 35 JPEG or WebP images; no link; text up to 2,200 characters.
  • LinkedIn: text with one image or one link, which needs a title; no video; text up to 3,000 characters.

Does easyCoexistence sit between your code and the networks?

Only where that saves you work: connecting, renewing tokens, forwarding comment and DM events and running the posts queue. Replies, reads and anything else go from your backend straight to the network's API with the customer's token, and Meta delivers a number's messages straight to your server. A feature a network adds is reachable from your code as soon as the network ships it, without waiting for a wrapper.

What happens when a new network joins?

It arrives as a new channel value on the same calls. Your connect sessions name it, its accounts appear in GET /channels, its events use the channel.* names, and each account costs what any other connection costs. A channel your account cannot use yet answers 400 channel_unavailable, and the message lists the channels open to it.

How to set it up

  1. Create a keyIn the dashboard under Profile, Developers, create the ec_live_ key and store it in your backend's secrets.
  2. Save a cardAdd a card to the account, since connect sessions answer 402 billing_required until one is saved.
  3. Connect each customerCreate a connect session with the channel and your customer's id as external_ref, and send the customer to its url.
  4. Set the webhooksGive each number a webhook_url and each social account a destination with PUT /channels/{id}/webhook.
  5. Post and replyPublish with POST /channels/{id}/posts and reply through each network's API with fresh credentials.

Common mistakes

  • Building DMs for TikTok, YouTube or LinkedIn. Those connections have no DMs, so plan comment replies there and replies to DMs for WhatsApp, Instagram and Messenger.
  • Sending an Instagram post without media. Instagram needs an image or a video, and the request is refused before it is queued, so attach media per network.
  • Storing channel_id and connection_id in one column without the kind. They are separate resources with separate IDs, so keep which one each value is.
  • Posting to LinkedIn from a feed with no review. LinkedIn's API terms restrict automated posting, so have a person approve each LinkedIn post first.
Doing this with EasyCoexistence

easyCoexistence gives your SaaS one integration for your customers' WhatsApp numbers and their Instagram, Facebook, TikTok, YouTube and LinkedIn accounts, and more channels: connect links, credentials, webhooks, status events and posts on each network's official API, with every connection monitored 24/7. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Can one endpoint receive events from all networks?

Yes. Point each channel's destination at the same URL and route on platform and account_id in the body. A WhatsApp number's messages come from Meta to its own webhook_url, which can be the same server.

Do I register my own app with Meta, TikTok, Google and LinkedIn?

No. Customers sign in through easyCoexistence's apps on those networks, and your backend receives the token it needs to call each network's API.

Which networks does the posts endpoint publish to?

Instagram, Facebook Pages, TikTok and LinkedIn. YouTube videos are uploaded through YouTube's own API with the channel's credentials.

How much does easyCoexistence's unified API cost?

The same on every network: US$ 9 to US$ 0.75 per connection per month, set by the band of your total count, with the first 3 days free.

Keep reading

Connect your first channel in two minutes.

No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.

  • 3 days free
  • Cancel any time
  • Official APIs only
  • Monitored 24/7

Verified on