Log inStart Free Trial
easyCoexistence Official APIs

Switching your SaaS from Ayrshare, Zernio or Unipile to easyCoexistence: what changes in your code

Switching your SaaS from Ayrshare, Zernio or Unipile to easyCoexistence changes four parts of your code: linking, now a hosted connect session per account; addressing, by channel_id or connection_id with your external_ref; posting, one POST /channels/:id/posts per account; and events, signed per account or sent by Meta straight to you. Each customer signs in once more, through the network's own consent screen.

Profile-Key

The header that sends an Ayrshare request to a User Profile, beside the Primary Profile's API key in Authorization.

5 minutes

Default validity of an Ayrshare linking URL from generateJWT; up to 2,880 minutes needs its Max Pack.

8 statuses

Zernio's post statuses: draft, pending_approval, scheduled, publishing, published, partial, failed and cancelled.

X-API-KEY

The header Unipile's API takes, on a base URL that is your own DSN, for calls such as the hosted auth link.

1 hour

How long an easyCoexistence connect link works; one link finishes with one number or one social sign-in.

What maps to what?

The concepts carry over; the shapes change. Your customer, the link that connects an account, the id you address it by, the post call and the events all have a counterpart. Each row follows the provider's own docs, read on 3 November 2026, and easyCoexistence's Partner API reference:

Ayrshare, Zernio or UnipileeasyCoexistence
Your customerAn Ayrshare User Profile, a Zernio profile or the name on a Unipile linkexternal_ref on each connect session, connection and event
LinkinggenerateJWT, GET /v1/connect/{platform} or POST /api/v1/hosted/accounts/linkPOST /connect-sessions, one account per link
AddressingProfile-Key, profileId with accountId, or account_idchannel_id for a social account, connection_id for a number
AuthenticationA Bearer key, with Profile-Key on Ayrshare; X-API-KEY on UnipileAuthorization: Bearer ec_live_…
PostingOne request with a list of platforms, on Ayrshare and ZernioPOST /channels/:id/posts, one per account
Incoming eventsThe provider's webhooksSigned forwards per account; WhatsApp from Meta to your URL

What changes when you leave Ayrshare?

The profile layer goes away. Ayrshare sends a post to a User Profile through the Profile-Key header and fans it out with a platforms list on POST /api/post, with scheduleDate in UTC and mediaUrls for the files. On easyCoexistence your loop runs over the customer's channels: one POST /channels/:id/posts each, with publish_at in any offset and media as {url, type}. Linking moves from generateJWT, whose URL lasts 5 minutes by default, to a connect session per account that lasts an hour.

Node.js: one post per channel instead of a platforms list
const EC = "https://easycoexistence.com/api/v1";
const auth = { Authorization: `Bearer ${process.env.EC_API_KEY}` };

// Before: POST https://api.ayrshare.com/api/post with Profile-Key,
// { post, platforms: ["instagram", "facebook"], mediaUrls, scheduleDate }
async function schedule(customerId, post) {
  const { data } = await fetch(`${EC}/channels?external_ref=${customerId}`, { headers: auth })
    .then((r) => r.json());
  for (const ch of data.filter((c) => post.networks.includes(c.channel) && c.status === "connected")) {
    await fetch(`${EC}/channels/${ch.id}/posts`, {
      method: "POST",
      headers: { ...auth, "Content-Type": "application/json", "Idempotency-Key": `${post.id}-${ch.id}` },
      body: JSON.stringify({
        text: post.text,
        media: post.mediaUrls.map((url) => ({ url, type: post.type })),
        publish_at: post.scheduleDate, // ISO 8601 with Z or an offset
      }),
    });
  }
}

What changes when you leave Zernio?

Less than from the others in posting. Zernio's POST /v1/posts takes content, a platforms list of platform and accountId, mediaItems and scheduledFor with a timezone, and honors an Idempotency-Key, as easyCoexistence does. The list becomes one call per channel_id, and scheduledFor becomes publish_at with an offset. Zernio's draft and pending_approval statuses have no counterpart, so drafts and approvals live in your product. Linking moves from GET /v1/connect/{platform} with profileId, which returns an authUrl, to POST /connect-sessions, which returns a url and later a channel_id on your redirect.

What changes when you leave Unipile?

Mostly messaging. Unipile links accounts through POST /api/v1/hosted/accounts/link on your DSN with X-API-KEY, sends with POST /api/v1/chats/{chat_id}/messages and reports new messages with a message_received webhook, which includes the account's own sent messages. On easyCoexistence, a WhatsApp number joins Meta's Cloud API through Coexistence, which needs the WhatsApp Business app, and Meta delivers its messages to your webhook_url. Replies go to the number's send_endpoint with the customer's token, and Instagram DMs go through Meta's API with the channel's credentials.

Do your customers have to reconnect?

Yes, once per account. The access each customer granted belongs to the provider's app that asked for it, so it cannot move to another one. Each account signs in again on a hosted connect link, through the network's own consent screen or Meta's popup for a WhatsApp number. Ask for it when the customer is at hand: each link works for an hour, and an account can hold 50 open links and create 100 an hour.

How do you switch without downtime?

Account by account, with both providers running side by side until each customer has moved. Your code routes each account to whichever provider holds it, and channel.connected or connection.connected is the moment to switch that account over:

  • Map each customer's id to external_ref, and store channel_id and connection_id beside it as they arrive.
  • Send connect links per customer, starting with the accounts that post or receive the most.
  • On channel.connected, schedule that account's pending posts on easyCoexistence, then cancel them at the old provider.
  • Point that account's events at your new receivers, then unlink it at the old provider.

What stays the same in your code?

Your product. The composer, the calendar, the approval flow and the inbox stay as they are, and only the adapter under them changes. Media still goes by public HTTPS link, idempotency still rides on a header, events are still verified with an HMAC over the raw body, and anything your code needs beyond the wrapped calls goes straight to the network's own API with the credentials from GET /channels/:id?credentials=1.

Common mistakes

  • Cancelling posts at the old provider before the account reconnects. Until channel.connected arrives, nothing can publish on easyCoexistence, so reschedule first and cancel second.
  • Moving a customer whose WhatsApp runs on the consumer app. Coexistence connects WhatsApp Business app numbers, so the customer moves the number to the WhatsApp Business app before opening the link.
  • Sending one link for all of a customer's networks. A link finishes with one number or one sign-in, so create one session per account.
  • Mapping cancelled to the same spelling. easyCoexistence reports canceled, with one l, so update any status comparison your code makes.
Doing this with EasyCoexistence

easyCoexistence gives your SaaS hosted connect links, fresh credentials, a publishing queue and signed events for your customers' WhatsApp numbers and their Instagram, Facebook, TikTok, YouTube and LinkedIn accounts, and more channels, each through the 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 I migrate my customers' connected accounts without them signing in again?

No. Each network ties the access to the app that requested it, so every account signs in once on an easyCoexistence connect link.

Does easyCoexistence connect X, Threads or Telegram?

Not today. Keep those accounts with your current provider while the others move. New networks join the same Partner API at the same price per connection as they are added.

Can I keep LinkedIn messaging from Unipile?

Keep it there. easyCoexistence works on LinkedIn Pages and profiles through posts and comments, and offers no LinkedIn DMs.

How much does easyCoexistence cost after switching?

US$ 9 to US$ 0.75 per connection per month, the same on every network and falling as you add connections, 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