JS Vision: V1 vs V2 Shifts API

If your Connecteam account has been migrated to JS Vision — our new shift-scheduling storage architecture — the Scheduler REST API gives you two paths to choose from. This section explains exactly how each one behaves on a migrated company, so you can pick the right one and migrate existing integrations safely.

👍

Just here to confirm nothing is breaking?

If your integration was written before JS Vision and only calls /scheduler/v1/..., it keeps working unchanged after migration:

• Every shift ID your system already stored continues to be accepted by V1 — no need to convert or re-fetch anything.
• The same endpoints, the same response shape, the same fields.

One thing to be aware of: any new shifts created via V1 after migration come back with a longer ID format (bson:uuid, around 61 characters, containing a :). If your shift-ID column is a fixed 24-char width, widen it before migration day. See Shift IDs and Response Shapes for the full mechanic.

TL;DR

Rule of thumb: if your integration was written before JS Vision, stay on V1 — your code keeps working as-is. If you want clean group-shift semantics or multi-spot open shifts, use V2.

Am I migrated?

Send any V2 request and check the response. You don't need a specific endpoint — just hit the list:

curl --request GET \
  --url 'https://api.connecteam.com/scheduler/v2/schedulers/{schedulerId}/shifts?startTime=1736899200&endTime=1737504000' \
  --header 'X-API-KEY: YOUR_API_KEY'

🚧

Non-migrated companies get 403

If your company is not migrated, every V2 endpoint returns:

JSON

{ "detail": "V2 endpoints require JS Vision migration. Contact support to migrate." }

There is no opt-in flag in the API — contact Connecteam Support to be migrated.

📘

Migrated companies see a normal response

A 200 with a shifts array (or a 404 for a missing shift, when calling by ID) means you're on Vision. Both V1 and V2 are available, and both run against the same data.

Pages in this section

See also

• Scheduler API Overview
• Shifts Overview
• API Reference