AutoFit import

AutoFit is another coaching platform. This module moves a coach’s whole AutoFit account into a Perform studio: trainees, programs, history, sub-coaches, templates, nutrition, PDF plans, content, recipes and forms. The same lane re-syncs an account later, for all data types or a subset. The routes on this page only verify, start, report and resume. The migration itself runs in a BullMQ worker, workers/autofit-import-worker.ts, on the queue PerformQueue.AUTOFIT_IMPORT.


Source	`backend/apps/core-api/src/modules/autofit-import/`
Lane	Web gateway only
Base path	`/v1/web/autofit-import`
Guards	`router.use(requireRole(StudioRole.OWNER, StudioRole.HEAD_COACH))` on every route

A run pulls an entire account into the studio, so a sub coach cannot reach any of these routes and gets FORBIDDEN (insufficient role). The module is not a five-file module. It has routes (with inline handlers), a schema, a service and a repository, plus the AutoFit API client, mappers (AutoFit rows to Perform shapes) and writers (Perform rows to the database), which the worker uses.

How it works

Auth model

AutoFit issues one master export key that covers several coaches. Perform holds it as the server secret AUTOFIT_MASTER_KEY. A run picks one coach from the key’s coach list by phone number. The key alone would let any studio type another coach’s number and pull their clients. A one-time code sent to that phone over WhatsApp is the proof of ownership. No run starts without it. Phone numbers are reduced to AutoFit’s coach_mobile form before matching: digits only, with no 972 country code and no leading zero. In responses a number is only ever shown masked, such as 054-***-5848.

Two lanes

Both lanes end in the same launchRun, so a run started from either is the same thing.

Lane	Routes	Used by
Settings wizard	`/ping`, `/request-otp`, `/start`	The original settings wizard. The phone and the code travel together in `/start`
Connect	`/connect/request-otp`, `/connect/verify`, `/connect/preview`, `/connect/start`	The onboarding step and the settings re-sync. Verification is its own step and leaves a marker, so the coach can read a preview and pick data types before starting

Data types

A run covers any subset of ten data types. Every flag defaults to true.

Flag	Covers
`trainees`	New trainees, with profile, transition subscription and photo
`trainingPrograms`	Every trainee’s in-app training programs
`history`	Weights, progress photos, steps and water
`coaches`	Sub-coaches as coach users, plus trainee assignments
`templates`	Training and nutrition templates into the template library
`nutrition`	The used foods and every trainee’s in-app nutrition plan
`pdfPlans`	Training and nutrition plans the coach sent as PDF files
`contents`	Courses and chapters as content items, with per-trainee unlocks
`recipes`	Recipes
`forms`	Form templates and every trainee’s past answers

Stages

A run’s status is its current stage. The worker walks only the stages its flags need (planOf), in this order:

Stage	When it is in the plan
`PULLING`	Always
`WRITING_LIBRARY`	Any of coaches, templates, nutrition, contents, recipes, forms, or when exercises are needed
`IMPORTING`	Trainees, coaches, or any per-trainee data type
`WRITING_PROGRAMS`	`trainingPrograms`

DONE follows the last stage in the plan. A run that fails moves to FAILED and records the stage it stopped in. A recipes-only re-sync is PULLING, WRITING_LIBRARY, DONE. The schema’s IMPORT_STAGES also lists MATCHING and REVIEW. In the worker code read for this page nothing sets a run to REVIEW. The two review routes below only act on a run in that status, so they appear to be unreachable in the current flow. This was not confirmed beyond the worker and this module.

Safety rules in the worker

These come from the worker’s header comment and explain behaviour you will see in the data:

Writes go straight through Prisma with no notifier, so an import can never send a WhatsApp or push to a trainee.
A trainee’s identity is externalUserId set to autofit:<id>, unique per studio, with a normalized phone fallback.
A trainee who existed in Perform before the import keeps their live status and dates. AutoFit only fills the profile.
Raw pulls are sealed with AES-GCM before they are written to R2, and the snapshot prefix is deleted when the run is done. When a new run starts, the snapshots of the studio’s earlier failed runs are deleted too.
Programs, templates, plans and form rows are keyed by the AutoFit id they carry in content.meta, so a re-run updates only rows the import wrote. See the AutoFit keys section on the Program templates page.

Limits

All counters live in Redis under perform:autofit-* keys with a 600 second window, unless noted.

Limit	Value	Scope
Phone checks through `/ping`	10 per minute	Per studio and user, in process memory
Phone lookups (pings and code sends, both lanes)	10 per window	Per studio
Code sends	5 per window	Per studio and phone
Code sends	10 per window	Per phone, across all studios
Code lifetime	300 seconds
Wrong attempts per code	5	The fifth miss burns the code
Code checks	10 per window	Per studio, and per user
Verified marker	30 minutes	Per studio

Codes and attempt counts are scoped per studio and phone, so another studio naming the same number can neither burn this studio’s code nor use up its sends.

Failure reasons

Most refusals carry a machine-readable reason in details.reason, next to the error code. The web side picks its copy by it.

{
  "ok": false,
  "code": "CONFLICT",
  "message": "an import is already running for this studio",
  "details": { "reason": "ALREADY_RUNNING", "importId": "cmimp00010qz8h1a2b3c4d" },
  "requestId": "req_01HZX4"
}

Reason	Code	When
`INVALID_PHONE`	`BAD_REQUEST`	Fewer than six digits after normalizing
`NO_SIGNUP_PHONE`	`BAD_REQUEST`	Connect lane with no phone given, no earlier synced account, and no phone on the caller’s coach row
`AUTOFIT_COACH_NOT_FOUND`	`NOT_FOUND`	No coach under the master key has this phone. Carries `phoneMasked`
`AUTOFIT_UNAVAILABLE`	`SERVICE_UNAVAILABLE`	The master key is not configured, or any AutoFit API failure. Carries `autofitCode` for an API failure
`RATE_LIMITED`	`RATE_LIMITED`	One of the Redis limits above
`SEND_FAILED`	`SERVICE_UNAVAILABLE`	The WhatsApp send failed, or no SmartSend sender is configured
`INVALID_CODE`	`BAD_REQUEST`	Wrong code, attempts remain
`CODE_BURNED`	`BAD_REQUEST`	Fifth wrong attempt. The coach must request a new code
`CODE_EXPIRED`	`BAD_REQUEST`	No code pending, or past the attempt cap
`NOT_VERIFIED`	`CONFLICT`	Connect preview or start with no verified marker
`ALREADY_RUNNING`	`CONFLICT`	The studio has a run that is not `DONE` or `FAILED`. Carries `importId`
`OTHER_ACCOUNT`	`CONFLICT`	The verified number is a different AutoFit account from the one synced before. Carries `lastPhoneMasked`
`LEGACY_MIGRATION`	`CONFLICT`	The studio was migrated by the earlier one-off scripts: it has trainees keyed `autofit:` but no run. A worker run would duplicate their data

The in-memory /ping limit throws RATE_LIMITED with no details.reason.

Ops master code

AUTOFIT_IMPORT_MASTER_CODE is an optional code that passes verification for any coach, so the team can run a migration for a customer without their phone in the loop. It is off when empty or shorter than six characters. It is compared in constant time, never consumes a pending code, counts against the code check limits, and every use is logged as a warning (autofit import: master code used). TRAINEE_OTP_DEV_MODE skips the WhatsApp send and returns the code in the response as devCode, for local testing.

Settings wizard endpoints

`POST /v1/web/autofit-import/ping`

Checks whether a phone number belongs to an AutoFit coach under the master key. Auth: web lane, OWNER or HEAD_COACH.

string

required

Trimmed, 6 to 20 characters. Normalized on the server.

Response:

{
  "ok": true,
  "data": {
    "coach": { "coachId": 1042, "coachName": "Noa Studio", "coachMobile": "500000000", "clients": 86 }
  }
}

Errors: RATE_LIMITED, and the reasons INVALID_PHONE, AUTOFIT_COACH_NOT_FOUND, AUTOFIT_UNAVAILABLE.

`POST /v1/web/autofit-import/request-otp`

Sends the verification code to the coach’s phone over WhatsApp. Auth: web lane, OWNER or HEAD_COACH.

string

required

Trimmed, 6 to 20 characters.

The service checks the studio is not a legacy migration, applies the lookup limit, resolves the coach, then issues a six-digit code. The code is stored in Redis for 300 seconds with a fresh attempt count and sent through the SmartSend template registercode in Hebrew. Response:

{
  "ok": true,
  "data": {
    "sent": true,
    "coach": { "coachId": 1042, "coachName": "Noa Studio", "coachMobile": "500000000", "clients": 86 }
  }
}

In dev mode the object also has devCode. Errors: reasons LEGACY_MIGRATION, RATE_LIMITED, INVALID_PHONE, AUTOFIT_COACH_NOT_FOUND, AUTOFIT_UNAVAILABLE, SEND_FAILED.

`POST /v1/web/autofit-import/start`

Verifies the code and starts a run. Auth: web lane, OWNER or HEAD_COACH.

string

required

The phone the code was sent to.

string

required

4 to 8 digits.

object

The ten data type flags. Each defaults to true, and the whole object defaults to all on.

In order: refuse when a run is active, refuse a legacy migration, check and spend the code, resolve the coach, then launch the run. Launching a run (launchRun):

Creates the AutofitImport row with status PULLING, the coach name, the normalized phone, the client count, and counters holding include, the stage plan, the kind (resync when the studio already finished a run, otherwise import) and startedBy.
A partial unique index allows one non-final run per studio. If two starts race, the slower one gets ALREADY_RUNNING.
Enqueues the job run with the import id on the AUTOFIT_IMPORT queue.
Deletes the R2 snapshots of the studio’s earlier failed runs.

Response:

{
  "ok": true,
  "data": {
    "importId": "cmimp00010qz8h1a2b3c4d",
    "coach": { "coachId": 1042, "coachName": "Noa Studio", "coachMobile": "500000000", "clients": 86 }
  }
}

Errors: reasons ALREADY_RUNNING, LEGACY_MIGRATION, RATE_LIMITED, INVALID_CODE, CODE_BURNED, CODE_EXPIRED, INVALID_PHONE, AUTOFIT_COACH_NOT_FOUND, AUTOFIT_UNAVAILABLE. VALIDATION (422) for a malformed body, such as a code that is not 4 to 8 digits.

`GET /v1/web/autofit-import/status`

The latest run in full, for the settings page and its report. Auth: web lane, OWNER or HEAD_COACH. No parameters. Returns { "run": null } when the studio has never run an import. Response:

{
  "ok": true,
  "data": {
    "run": {
      "id": "cmimp00010qz8h1a2b3c4d",
      "status": "DONE",
      "coachName": "Noa Studio",
      "clientCount": 86,
      "counters": { "total": 86, "pulled": 86, "imported": 84, "processed": 86, "clientErrors": 2 },
      "report": {
        "clients": 84,
        "programs": 131,
        "coachesCreated": 2,
        "templates": 18,
        "coaches": [
          { "name": "Omer", "email": "omer@example.com", "phone": "+972 500000001", "tempPassword": "TEMP_PASSWORD" }
        ]
      },
      "credentials": [
        { "name": "Omer", "email": "omer@example.com", "phone": "+972 500000001", "tempPassword": "TEMP_PASSWORD" }
      ],
      "error": null,
      "createdAt": "2026-10-04T08:00:00.000Z",
      "finishedAt": "2026-10-04T08:41:00.000Z"
    }
  }
}

The counter and report keys in the example are a subset. Both objects are written by the worker.

counters is the worker’s live bookkeeping with two keys removed: coachReport (sealed credentials) and phoneMarks.
report is set when the run is done.
Sub-coach passwords. The import creates logins for sub-coaches with a temporary password. Reports store those passwords sealed. presentReport opens them with BETTER_AUTH_SECRET for an owner or head coach, which is every caller of this router. A password that fails to open, for example after the secret was rotated, reads as null.
credentials merges the sub-coach rows of every finished run, newest first, one per coach (by email, else name and phone). A row that still carries a password wins over a later one that does not. It is returned whatever the latest run’s status, so a running or failed re-sync never hides the credentials from the first import.

Errors: UNAUTHORIZED, FORBIDDEN.

`GET /v1/web/autofit-import/matches`

Lists the exercise matches of a run that is waiting for review. Auth: web lane, OWNER or HEAD_COACH. Requires the studio’s active run to have status REVIEW. See the note under Stages about whether that status is reachable. Response:

{
  "ok": true,
  "data": {
    "importId": "cmimp00010qz8h1a2b3c4d",
    "matches": [
      {
        "id": "cmmatch0010qz8h1a2b3c4d",
        "name": "Bench press",
        "nameEn": "bench press",
        "status": "PROPOSED",
        "autofitVideo": "https://autofit.example.com/videos/123.mp4",
        "proposedExerciseId": "cmexr8s9t0004qz8h2u3v4w5x",
        "proposedExerciseName": "Bench press",
        "proposedVideoUrl": "https://media.example.com/exercises/0025.mp4",
        "confidence": 0.92,
        "candidates": []
      }
    ]
  }
}

Errors: CONFLICT (no import is waiting for review).

`POST /v1/web/autofit-import/review`

Submits the coach’s decisions on exercise matches and continues the run. Auth: web lane, OWNER or HEAD_COACH.

object[]

required

At most 2000 entries.

string

required

The match id. Must belong to the run under review.

string

required

confirm, create or link.

string

Required when action is link. An exercise the studio can see.

Action	Effect on the match
`confirm`	Status `CONFIRMED`, resolved to the proposed exercise. Fails if there is no proposal or the proposed exercise no longer exists
`link`	Status `CONFIRMED`, resolved to the exercise the coach picked
`create`	Status `CREATE_NEW`, resolved to nothing. The worker creates a new exercise

Decisions are applied one at a time, with no transaction. A failure part way through leaves the earlier decisions saved. After the loop, every match still PROPOSED is set to CREATE_NEW, the run moves to WRITING_PROGRAMS, and the job is enqueued again. Response:

{
  "ok": true,
  "data": { "ok": true }
}

Errors: CONFLICT (no import is waiting for review). BAD_REQUEST for unknown match in review, a confirm with no proposal, a proposal that no longer exists, link decision without an exercise, or picked exercise not found. VALIDATION.

`POST /v1/web/autofit-import/resume`

Resumes the latest run after a failure. Auth: web lane, OWNER or HEAD_COACH. No body. The latest run must be FAILED, and the stage it failed in (counters.failedStage) must be one of PULLING, WRITING_LIBRARY, IMPORTING, MATCHING, WRITING_PROGRAMS. The run’s status is set back to that stage, its error is cleared, and the job is enqueued again. No new code is needed. Response:

{
  "ok": true,
  "data": { "importId": "cmimp00010qz8h1a2b3c4d", "stage": "IMPORTING" }
}

Errors: CONFLICT (no failed import to resume, or this import cannot be resumed).

Connect endpoints

`POST /v1/web/autofit-import/connect/request-otp`

Sends the verification code, without revealing whose account the number is. Auth: web lane, OWNER or HEAD_COACH.

string

Optional. null or a blank string counts as not sent.

The phone to prove is chosen in this order:

The phone in the body. This is the “AutoFit is on a different number” path.
The AutoFit account the studio synced before, so a re-sync asks the same account again.
The phone on the caller’s own coach row, the one they verified at signup.

Unlike the settings lane, nothing about the coach comes back before the code is verified. Response:

{
  "ok": true,
  "data": { "sent": true, "phoneMasked": "050-***-0000" }
}

In dev mode the object also has devCode. Errors: reasons LEGACY_MIGRATION, INVALID_PHONE, NO_SIGNUP_PHONE, RATE_LIMITED, AUTOFIT_COACH_NOT_FOUND, AUTOFIT_UNAVAILABLE, SEND_FAILED.

`POST /v1/web/autofit-import/connect/verify`

Checks the code and leaves a verified marker for the studio. Auth: web lane, OWNER or HEAD_COACH.

string

Optional. Must match what was used in the request step. The same fallback order applies.

string

required

4 to 8 digits.

The coach is resolved before the code is spent, so an AutoFit hiccup at this point leaves the code valid for a retry. On success a marker with the phone, the coach id and name, the client count and the time is stored in Redis at perform:autofit-verified:<studioId> for 30 minutes. That is long enough to read the preview and pick data types. A new verification replaces the marker. Response:

{
  "ok": true,
  "data": { "verified": true, "coach": { "coachName": "Noa Studio", "clients": 86 } }
}

Errors: reasons INVALID_PHONE, NO_SIGNUP_PHONE, RATE_LIMITED, INVALID_CODE, CODE_BURNED, CODE_EXPIRED, AUTOFIT_COACH_NOT_FOUND, AUTOFIT_UNAVAILABLE. VALIDATION.

`GET /v1/web/autofit-import/connect/preview`

Counts of what the import would bring, and what is already in the studio, for the confirm screen. Auth: web lane, OWNER or HEAD_COACH. Requires a verified marker. No parameters. The preview asks AutoFit at most once per section, with no retries and an 8 second timeout. A busy or slow AutoFit means “no number”, not an error.

counts.trainees comes from the marker.
trainingPlans, nutrition and pdfPlans come from the paged client listing. They are null for an account with more than 3000 clients, or when the listing fails.
coaches, coachesWithoutEmail, templates, contents and recipes come from one library export. When a section came back whole, the import’s own mappers count it, so the number matches what a run would write. Past the row limit, the table’s total stands in as an upper bound.
coachesWithoutEmail counts sub-coaches that cannot become a login and will be skipped.
forms and history are always null. Only a full export shows them.
existing says what earlier runs already put in the studio, per row.
partial is true when any asked count is null.
isResync is true when the studio already finished a run.

The preview is cached in Redis under a key tied to the marker, for the rest of the marker’s life. A partial preview is rebuilt once it is 60 seconds old. Response:

{
  "ok": true,
  "data": {
    "coachName": "Noa Studio",
    "phoneMasked": "050-***-0000",
    "counts": {
      "trainees": 86,
      "trainingPlans": 71,
      "nutrition": 64,
      "pdfPlans": 12,
      "coaches": 3,
      "coachesWithoutEmail": 1,
      "templates": 18,
      "contents": 24,
      "recipes": 40,
      "forms": null,
      "history": null
    },
    "existing": {
      "trainees": 0,
      "trainingPlans": 0,
      "nutrition": 0,
      "pdfPlans": 0,
      "templates": 0,
      "contents": 0,
      "recipes": 0,
      "forms": 0,
      "coaches": 0
    },
    "partial": false,
    "isResync": false
  }
}

Errors: reason NOT_VERIFIED.

`POST /v1/web/autofit-import/connect/start`

Starts a run from the verified marker. Auth: web lane, OWNER or HEAD_COACH. Requires a verified marker.

object

The ten data type flags. All default to true.

boolean

default:"false"

Set to true to confirm that a second AutoFit account is meant to land in this studio.

Checks run in this order: an active run, a legacy migration, the marker, then the account check. If the studio synced a different AutoFit number before and confirmOtherAccount is not true, the request is refused with OTHER_ACCOUNT. This stops a mistyped number from merging a second account into the studio. The marker is kept, so the confirmed retry needs no new code. On success the run is launched exactly as in the settings lane, and the marker and its preview cache are deleted. One verification gives one run. Response:

{
  "ok": true,
  "data": { "importId": "cmimp00010qz8h1a2b3c4d" }
}

Errors: reasons ALREADY_RUNNING, LEGACY_MIGRATION, NOT_VERIFIED, OTHER_ACCOUNT.

Progress endpoint

`GET /v1/web/autofit-import/sync`

A slim view of the latest run, for the progress bar on the home page. Auth: web lane, OWNER or HEAD_COACH. No parameters. Every manager with the dashboard open polls this every few seconds, so it is one database read and a whitelist: numbers and flags only. It never carries the growing id lists or the sealed credentials. Returns { "run": null } when there has been no run. Response:

{
  "ok": true,
  "data": {
    "run": {
      "id": "cmimp00010qz8h1a2b3c4d",
      "status": "IMPORTING",
      "clientCount": 86,
      "createdAt": "2026-10-04T08:00:00.000Z",
      "finishedAt": null,
      "error": null,
      "failedStage": null,
      "plan": ["PULLING", "WRITING_LIBRARY", "IMPORTING", "WRITING_PROGRAMS"],
      "include": {
        "trainees": true,
        "trainingPrograms": true,
        "history": true,
        "coaches": true,
        "templates": true,
        "nutrition": true,
        "pdfPlans": true,
        "contents": true,
        "recipes": true,
        "forms": true
      },
      "kind": "import",
      "counters": { "pullStarted": true, "total": 86, "pulled": 86, "imported": 41, "processed": 43, "clientErrors": 2 },
      "report": null,
      "delta": null
    }
  }
}

Field	Meaning
`failedStage`	The stage a `FAILED` run stopped in. `null` for every other status
`plan`	The stages this run walks, in order. `DONE` follows the last
`kind`	`import` for a first run, `resync` for a later one
`counters`	Only these keys, when they hold a number or boolean: `pullStarted`, `total`, `pulled`, `libraryPulled`, `libraryStepsDone`, `libraryStepsTotal`, `exercisesFound`, `imported`, `processed`, `clientErrors`, `programs`, `programsTotal`
`report`	`null` until the run is done. Then twelve numbers: `clients`, `programs`, `coachesCreated`, `coachesExisting`, `coachesSkipped`, `templates`, `nutritionPlans`, `pdfPlans`, `contents`, `recipes`, `formTemplates`, `formResponses`
`delta`	`null` until done. Then, per data type, `created`, `updated` and `kept`

Errors: UNAUTHORIZED, FORBIDDEN.

Environment variables

Name	Purpose
`AUTOFIT_MASTER_KEY`	The AutoFit master export key
`AUTOFIT_MINUTE_BUDGET`	Export requests per minute the client paces itself to
`AUTOFIT_IMPORT_MASTER_CODE`	Optional ops code accepted for any coach
`BETTER_AUTH_SECRET`	Opens the sealed sub-coach passwords in a report
`SMARTSEND_OTP_API_KEY`, `SMARTSEND_API_KEY`	The SmartSend sender for the code. The first is preferred
`TRAINEE_OTP_DEV_MODE`	Skips the WhatsApp send and returns the code
`R2_ENDPOINT`, `R2_REGION`, `R2_ACCESS_KEY_ID`, `R2_SECRET_ACCESS_KEY`, `R2_BUCKET_NAME`, `R2_PUBLIC_BASE_URL`, `R2_PATH_PREFIX`	Storage for run snapshots and mirrored media

Never put the value of any of these in documentation, tickets or logs.

API basics

Trainees

Plans and libraries

Tracking

Imports

Forms

Tasks and automation

Communication

Studio and billing

Admin and internal services

Trainee app API

Partner and automation

Public, internal and auth

How it works

Auth model

Two lanes

Data types

Stages

Safety rules in the worker

Limits

Failure reasons

Ops master code

Settings wizard endpoints

`POST /v1/web/autofit-import/ping`

`POST /v1/web/autofit-import/request-otp`

`POST /v1/web/autofit-import/start`

`GET /v1/web/autofit-import/status`

`GET /v1/web/autofit-import/matches`

`POST /v1/web/autofit-import/review`

`POST /v1/web/autofit-import/resume`

Connect endpoints

`POST /v1/web/autofit-import/connect/request-otp`

`POST /v1/web/autofit-import/connect/verify`

`GET /v1/web/autofit-import/connect/preview`

`POST /v1/web/autofit-import/connect/start`

Progress endpoint

`GET /v1/web/autofit-import/sync`

Environment variables

​How it works

​Auth model

​Two lanes

​Data types

​Stages

​Safety rules in the worker

​Limits

​Failure reasons

​Ops master code

​Settings wizard endpoints

​POST /v1/web/autofit-import/ping

​POST /v1/web/autofit-import/request-otp

​POST /v1/web/autofit-import/start

​GET /v1/web/autofit-import/status

​GET /v1/web/autofit-import/matches

​POST /v1/web/autofit-import/review

​POST /v1/web/autofit-import/resume

​Connect endpoints

​POST /v1/web/autofit-import/connect/request-otp

​POST /v1/web/autofit-import/connect/verify

​GET /v1/web/autofit-import/connect/preview

​POST /v1/web/autofit-import/connect/start

​Progress endpoint

​GET /v1/web/autofit-import/sync

​Environment variables

How it works

Auth model

Two lanes

Data types

Stages

Safety rules in the worker

Limits

Failure reasons

Ops master code

Settings wizard endpoints

`POST /v1/web/autofit-import/ping`

`POST /v1/web/autofit-import/request-otp`

`POST /v1/web/autofit-import/start`

`GET /v1/web/autofit-import/status`

`GET /v1/web/autofit-import/matches`

`POST /v1/web/autofit-import/review`

`POST /v1/web/autofit-import/resume`

Connect endpoints

`POST /v1/web/autofit-import/connect/request-otp`

`POST /v1/web/autofit-import/connect/verify`

`GET /v1/web/autofit-import/connect/preview`

`POST /v1/web/autofit-import/connect/start`

Progress endpoint

`GET /v1/web/autofit-import/sync`

Environment variables