← All posts
Changelog

UnifyPort Exporter Is Live: A One-Click Browser Extension for Connecting X and TikTok Accounts — UnifyPort

What shipped

UnifyPort Exporter (v1.0.0) is now live on the Chrome Web Store. It’s a 37 KB browser extension that does one thing: while you’re logged into X (Twitter) or TikTok in your browser, it captures the session context for that account and saves it as a JSON file on your machine — nothing is uploaded, nothing is sent to a third party.

That JSON file is the missing piece in UnifyPort’s auth_mode=session connection flow. Until now, getting a valid session export for X or TikTok meant reaching for a separate tool or doing it manually. UnifyPort Exporter turns that into: log in, click the icon, click export, done.

X (Twitter): session import, end to end

X has supported auth_mode=session since the v1 API shipped — you provide an existing authorized session and UnifyPort completes the import. The flow looks like this:

1. Create the account record

POST /v1/accounts
Content-Type: application/json

{
  "provider": "twitter",
  "auth_mode": "session"
}

2. Export the session with UnifyPort Exporter

Open X in your browser, make sure you’re logged into the account you want to connect, click the UnifyPort Exporter icon, and choose Export X session. The extension writes a JSON file containing the cookies and page user/session context for that account.

3. Import the session

POST /v1/accounts/{account_id}/auth/session/import
Content-Type: application/json

{
  "params": {
    "session_url": "<reference to the exported session JSON>",
    "pin": "0000"
  }
}

params.pin only matters if the account has 2FA enabled — the default is 0000. If you need geographic routing for the connection, params.proxy_config is also accepted at this step.

4. Bring the runtime online

Once the import response confirms the session is valid, start the runtime as usual:

POST /v1/accounts/{account_id}/runtime/start

From here, X messages arrive as message.received events on your webhook, in the same normalized schema as every other channel.

TikTok: the same one-click export

TikTok has no official DM API — teams that need to receive TikTok messages already rely on UnifyPort’s session-based connection for that channel (see our earlier post on receiving TikTok messages without a DM API). UnifyPort Exporter adds a TikTok session export option alongside the X one, using the same pattern: log in, click export, get a JSON file you can hand to the account-connection flow.

For both platforms, the extension requires you to already be logged into the target account in your browser — it doesn’t handle login itself, it just captures the session that’s already there.

Privacy and scope

A few things worth calling out, straight from the listing:

  • Local only. The export is written to your computer as a JSON file. UnifyPort Exporter doesn’t transmit it anywhere on its own.
  • Two platforms today. v1.0.0 supports X and TikTok. If your team connects WhatsApp, Telegram, LINE, or Zalo, those providers already have their own code/QR/session flows through /v1/accounts/{id}/auth/session/* and don’t need the extension.
  • No data resale. The developer (unifyport.ai) states the extension does not collect, sell, or transfer user data to third parties outside its core function.

How to start

  1. Install UnifyPort Exporter from the Chrome Web Store.
  2. Log into X or TikTok in the same browser.
  3. Click the extension icon and export the session for the account you want to connect.
  4. Create the account via POST /v1/accounts with provider: "twitter" (or your TikTok provider) and auth_mode: "session".
  5. Import the exported session via /auth/session/import, then start the runtime.

If you’re already running UnifyPort for WhatsApp or Telegram inbound and have been putting off adding an X or TikTok channel because the session-export step felt fiddly, this removes that excuse — it’s now a two-click setup on top of the same unified webhook you’re already consuming.