Drıftstack docs
Docs

Export and import profiles (API only)

You might be here because: “export my profile” · “import a profile file” · “give a profile to a teammate” · “move a profile to another account” · “the imported profile has no cookies” · “does the export include my proxy password” · “400 ValidationFailed on import” · “where is Export in the app”

Short answer

Export and import work only from code (the API) today; the desktop app does not show them. Export writes a profile to a JSON file that holds its name, device, description and notes — not its cookies, logins or proxy — and import reads that file and creates a fresh profile, in the same account or another. That is how you hand a profile to a teammate or move it between accounts.

Check first

  • Expecting logins to travel with it? Browser state is not in the file. Cookies move separately (see the cookies page).
  • Room for one more profile? An import is a new profile and counts against the plan’s number (429 when you are at it).
  • Imported a lot this month? Imports are capped at twice your plan’s saved-profile number each calendar month; the count starts again on the 1st of each month (UTC) (429).

Likely causes and fixes

  1. No Export or Import button in the app. They are switched off in the desktop app for now. Fix: use the API (below).

  2. The imported profile has no proxy. The file never carries one. Fix: Edit the profile and choose a proxy before launching.

  3. The name already exists (409). Import uses the name in the file unless you give another; from code, name_override renames without editing the file. Fix: rename, or delete the profile holding that name.

  4. The device is no longer offered (400). The device in the file must be in the current device catalogue and open for new profiles: an older retained profile still exports, but its file cannot be imported. Fix: create a new profile on a device your plan offers.

  5. The device is not on your plan (403). An import is refused when your plan does not include the file’s device. Fix: choose a plan that includes it, or create a new profile on a device your plan offers.

  6. From code. GET /v1/profiles/{id}/export returns the file; POST /v1/profiles/import with { "envelope": <the file>, "name_override"?: "…" } creates the profile. Export needs a key with read scope; import needs write:profiles (a broad write key also works), and a team admin can import into the owner’s workspace. Notes travel; a file exported before notes existed imports with none.

If it still fails

Press Talk to a person in this chat (or open Help) and include the exact error the import returned, the device named in the file, and whether the file came from another account.