Direct transfers

Import selected provider profiles into local TabGecko profiles after preview. This is a limited data mapping, not a clone of another browser installation.

Supported sources

Source value	Pagination and limits
gologin	Pass returned next as page.
dolphin	Pass returned next as cursor unchanged, including a page: prefix from the legacy-list fallback.
multilogin	Multilogin X only. Pass next as page; 30 profiles per page and maximum offset 10,000. Legacy Multilogin 6 is unsupported.

List → preview → execute

POST /api/v1/integrations/transfers/list

{
  "source": "gologin",
  "token": "<PROVIDER_TOKEN>",
  "page": 1
}

POST /api/v1/integrations/transfers/preview

{
  "source": "gologin",
  "token": "<PROVIDER_TOKEN>",
  "ids": [
    "PROVIDER_PROFILE_ID"
  ],
  "cookies": false
}

POST /api/v1/integrations/transfers/execute

{"id":"<PREVIEW_UUID>"}

The Authorization header always contains the local API token. The token field in list/preview is the separate provider credential. All three operations require profiles:write. List and preview do not create local profiles. Review every row and all warnings, then execute the approved preview with the same local token. The provider token is not saved by this transfer flow.

Exact transfer bounds

1–20 unique selected profile IDs per preview. Each provider response and the combined selected profile/cookie data are limited to 8 MiB. Provider request deadline: 15 seconds.
A preview lives in memory for ten minutes, belongs to its local token and is single-use. Restarting the app loses it. At most 20 stored previews, four previews being prepared and one execute operation at a time.
Invalid rows prevent execution. Already imported active provider profiles are skipped, not overwritten. Inspect created, failed, skipped and each result; an execute response is not a promise of all-row success.
If the execute response is lost, inspect local profiles before retrying. The preview is consumed before execution; creating another preview is a new operation. Source profiles are read, not deleted or edited.

What is and is not transferred

Mapped when available: name, plain-text notes, browser type, OS, User-Agent, resolution, string tags, supported custom HTTP/HTTPS/SOCKS4/SOCKS5 proxy and optional cookies. Other fingerprint fields, extensions, saved logins, tabs and local browser folders are not copied. Noise seeds are newly generated. Cookie import can be queued; queued does not mean verified in a running browser.

Multilogin X transfers only metadata that the provider returns; automatically generated fingerprint values can be absent. Built-in Multilogin proxies are rejected. Cookie export requires the signed-in local Multilogin launcher on port 45001 and a folder ID. Provider permissions, plan restrictions and service availability still apply. No identical-fingerprint or full-session guarantee is made.