Shifts · Tenvelo API

GET/v1/scheduled-shifts

List the plan for a day at a location

No. listScheduledShiftsAuth pos:shifts:read
Returns one site's planned shifts for one day the site counts: who is on the rota, and for when. The plan, never the price — cost is the labour gate's (GET /v1/reports/rota), and a counter showing who is expected has no business with what they cost.
A till reads this against the shifts it records, which is how a manager sees who did not show up; it is a live read like the roster, never on the change feed, and a call to but one site.
Parameters

location_idquery · string · uuid
Required
The site whose plan is asked for.

business_datequery · string · date
Required
The trading day, as that site counts it.

cursorquery · string
Opaque cursor from a previous page's next_cursor. Omit to start from the beginning.
Pass it back exactly as received. It is base64 and its structure is not part of this contract — decoding it, or constructing one by hand, will break without notice.

limitquery · integer · int32
Maximum items to return. The server may return fewer, so always drive the loop from has_more rather than from the size of the page you got back.
Responses

200
The plan for the day at the site, each shift with the member it names.

PlannedShiftPage · application/json

has_moreboolean

Required
Whether another page follows.

itemsarray of PlannedShift

Required

idstring · uuid

Required

ends_atstring · date-time

Required
After starts_at.

member_idstring · uuid

Required
The member's user id.

member_namestring

Required
The member's name, joined for display; never written by a client.

starts_atstring · date-time

Required

next_cursorstring

Nullable
Opaque cursor for the next page, or null on the last page. Pass it back verbatim as the cursor query parameter; its contents are not part of this contract.

400
The request could not be parsed. Malformed JSON, a bad query parameter, or a header that failed to decode, among them an API-Version later than the server speaks or not a date (api-version-unknown, with the server's own in api_version).
Distinct from 422: a 400 never reached validation, so invalid_params is absent. Retrying without changing the request will fail again, except that a request refused for its API-Version goes once the server is updated.

401
No credentials, or credentials that could not be verified — missing bearer token, malformed JWT, expired token, or a signature that failed against the issuer's JWKS.
Refresh the token and retry once. Repeated 401 after a refresh means the device needs to re-enrol.

403
Authenticated, but not permitted. The token is valid and its merchant was resolved, but the caller's role does not allow this operation, or the target belongs to a different merchant.
Cross-tenant access is reported as 403 on a resource the caller may not see, and as 404 where even confirming existence would leak information. Retrying will not help.

410
The request names an API-Version this server no longer serves (docs/decisions/0011). Nothing in it was read. api_version names the version the server speaks: the client is behind, and sends the request again once it is updated.

422
The request parsed but failed validation.
invalid_params lists every failing field with a JSON Pointer, not just the first, so a client can mark up a whole form in one pass rather than making the user fix errors one round trip at a time.
Also returned when an Idempotency-Key is replayed with a different body, and when device-computed order totals disagree with the server's recomputation.

429
Rate limit exceeded. Honour Retry-After rather than applying your own backoff.
A fleet of tills coming back online together after an outage is the realistic cause, which is exactly when uncoordinated client-side retry turns a brief outage into a sustained one. The limit is per process, and per site for what records trade there — a request spends its site's budget, and a till's own smaller one inside it — and per (client, merchant) for everything else; no RateLimit field is sent, so this response and its Retry-After are the whole of the contract.

500
Something failed on our side. trace_id identifies the request in our tracing — quote it in a support ticket.
The body never carries internal detail: no SQL, no stack traces, no upstream error strings. Safe to retry with the same Idempotency-Key.
Request
curl -X GET 'https://api.tenvelo.com/v1/scheduled-shifts?location_id=…&business_date=…' \ -H "Authorization: Bearer $TOKEN"
Response
{ "has_more": false, "items": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "ends_at": "2026-09-11T09:30:00Z", "member_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "member_name": "string", "starts_at": "2026-09-11T09:30:00Z" } ], "next_cursor": "string" }
GET/v1/shifts

List shifts

No. listShiftsAuth pos:shifts:read
Returns the merchant's shifts, newest first, filterable by location, member, state and business date.
GET /v1/shifts/{id} has existed since shifts did and there was no way to find an id: a client could read a shift it already knew about and could not discover one. This is that gap. A till does not need it — a device knows its own open shift — so it is a manager's read and an integration's, under the shift read scope.
Times are as the till recorded them. A manager's correction is a separate record and is applied by the reports that pay from these hours (GET /v1/reports/shifts and GET /v1/reports/timesheets), not here: this is the device's account of what happened, and overwriting it in the resource would leave nothing to compare a correction against.
Parameters

cursorquery · string
Opaque cursor from a previous page's next_cursor. Omit to start from the beginning.
Pass it back exactly as received. It is base64 and its structure is not part of this contract — decoding it, or constructing one by hand, will break without notice.

limitquery · integer · int32
Maximum items to return. The server may return fewer, so always drive the loop from has_more rather than from the size of the page you got back.

location_idquery · string · uuid
Only shifts worked at this location.

member_idquery · string · uuid
Only shifts worked by this member.

statusquery · string · enum
Only shifts in this state. Absent returns both.

fromquery · string · date
Only shifts whose clock-in falls on or after this business date, in the location's clock.

toquery · string · date
Only shifts whose clock-in falls on or before this business date.
Responses

200
A page of shifts.

ShiftPage · application/json

has_moreboolean

Required
Whether another page follows.

itemsarray of Shift

Required

idstring · uuid

Required
UUIDv7, minted by the device.

breaksarray of ShiftBreak

Every break the till recorded on the shift, earliest first. A break is its own row keyed by the id the device minted, so a second break is appended rather than overwriting the first.

idstring · uuid

Required
UUIDv7, minted by the device.

ended_atstring · date-time

Nullable
When the break ended, or null while the member is still on it.

shift_idstring · uuid

Read only
The shift the break belongs to.

started_atstring · date-time

Required
When the break started, as the device saw it.

clock_in_atstring · date-time

Required
When the staff member clocked in, as the device saw it. Provided for reporting and display; the server stamps its own receipt time, because a till that has been off for a week comes back with a clock hours out.

clock_out_atstring · date-time

Nullable
When the staff member clocked out, or null while the shift is open.

created_atTimestamp

RequiredRead only
Server-assigned RFC 3339 timestamp, always UTC.
Server-assigned because device clocks drift and cannot be trusted for ordering — a till that has been powered off for a week may come back with a clock hours out. Where the device's own view of time matters it is carried separately in client_created_at.

device_idstring · uuid

Required
The till the staff member worked on.

location_idstring · uuid

Required
The location the staff member worked at.

member_idstring · uuid

Required
The staff member (a user on this merchant's roster).

merchant_idstring · uuid

RequiredRead only

statusstring · enum

Required
An open shift is in progress; a closed one has a clock-out time. The two are stated together so a shift can never be recorded in a state nobody expects.
openclosed

updated_atTimestamp

RequiredRead only
Server-assigned RFC 3339 timestamp, always UTC.
Server-assigned because device clocks drift and cannot be trusted for ordering — a till that has been powered off for a week may come back with a clock hours out. Where the device's own view of time matters it is carried separately in client_created_at.

versionVersion

RequiredRead only
Optimistic concurrency version, raised by the server on every write. A version is never lower than one already returned for the resource, though it may rise by more than one.
Returned in the ETag response header as well as in the body. Send it back in If-Match on an update and the write is rejected with 412 if anyone else has written since — which is what stops two tills silently overwriting each other's edit to the same product when both come back online at once.
≥ 1

next_cursorstring

Nullable
Opaque cursor for the next page, or null on the last page. Pass it back verbatim as the cursor query parameter; its contents are not part of this contract.

400
The request could not be parsed. Malformed JSON, a bad query parameter, or a header that failed to decode, among them an API-Version later than the server speaks or not a date (api-version-unknown, with the server's own in api_version).
Distinct from 422: a 400 never reached validation, so invalid_params is absent. Retrying without changing the request will fail again, except that a request refused for its API-Version goes once the server is updated.

401
No credentials, or credentials that could not be verified — missing bearer token, malformed JWT, expired token, or a signature that failed against the issuer's JWKS.
Refresh the token and retry once. Repeated 401 after a refresh means the device needs to re-enrol.

403
Authenticated, but not permitted. The token is valid and its merchant was resolved, but the caller's role does not allow this operation, or the target belongs to a different merchant.
Cross-tenant access is reported as 403 on a resource the caller may not see, and as 404 where even confirming existence would leak information. Retrying will not help.

410
The request names an API-Version this server no longer serves (docs/decisions/0011). Nothing in it was read. api_version names the version the server speaks: the client is behind, and sends the request again once it is updated.

422
The request parsed but failed validation.
invalid_params lists every failing field with a JSON Pointer, not just the first, so a client can mark up a whole form in one pass rather than making the user fix errors one round trip at a time.
Also returned when an Idempotency-Key is replayed with a different body, and when device-computed order totals disagree with the server's recomputation.

429
Rate limit exceeded. Honour Retry-After rather than applying your own backoff.
A fleet of tills coming back online together after an outage is the realistic cause, which is exactly when uncoordinated client-side retry turns a brief outage into a sustained one. The limit is per process, and per site for what records trade there — a request spends its site's budget, and a till's own smaller one inside it — and per (client, merchant) for everything else; no RateLimit field is sent, so this response and its Retry-After are the whole of the contract.

500
Something failed on our side. trace_id identifies the request in our tracing — quote it in a support ticket.
The body never carries internal detail: no SQL, no stack traces, no upstream error strings. Safe to retry with the same Idempotency-Key.

503
Temporarily unable to serve the request — a dependency is down or the service is shedding load.
Retry with the same Idempotency-Key after Retry-After. This is always safe: a request that did take effect before the failure will be recognised as a replay.
Request
curl -X GET 'https://api.tenvelo.com/v1/shifts' \ -H "Authorization: Bearer $TOKEN"
Response
{ "has_more": false, "items": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "breaks": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "ended_at": "2026-09-11T09:30:00Z", "shift_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "started_at": "2026-09-11T09:30:00Z" } ], "clock_in_at": "2026-09-11T09:30:00Z", "clock_out_at": "2026-09-11T09:30:00Z", "created_at": "2026-09-08T09:41:12Z", "device_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "location_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "member_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "merchant_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "status": "open", "updated_at": "2026-09-08T09:41:12Z", "version": 7 } ], "next_cursor": "string" }
POST/v1/shifts/batch-upsert

Submit shifts

No. batchUpsertShiftsAuth pos:shifts:write
Submits shifts a client has queued — a till's staff clock-in/out while it was offline, or one clock event sent the moment it happened.
The client mints every shift's id, so a retried batch converges on the same records rather than opening second shifts. Each item carries its own idempotency_key and stands or falls on its own: an invalid or refused item fails in its result, and every other item is still applied.
A shift arrives open to clock a member in, and is written once more as closed — with the version it was written from, and the clock_out_at the device saw — when the member clocks out. It is one record throughout: the id the device minted is the id of the shift. A member already on an open shift is refused with 409. A break is sent as a row in the shift's breaks array, keyed by a device-minted id; the server appends it, and a retried batch converges on the same row rather than duplicating the break.
Request body application/json · ShiftBatchUpsertRequest

itemsarray of ShiftBatchUpsertItem

Required
≥ 1 items · ≤ 500 items

hlcHLC
A hybrid logical clock stamp (Kulkarni et al., 2014): the recorder's wall clock in milliseconds in the high 48 bits and a counter in the low 16, a 64-bit integer written as its decimal digits in a string. A stamp is past 2^53, beyond the integers a JSON number holds exactly as most parsers read it, so I-JSON writes it as a string (RFC 7493 §2.2).
A device stamps every fact it records, as it records it, after every stamp it has made or pulled — every change on the feed carries one — so a fact recorded after seeing another ranks after it whatever either wall clock says. The stamp is when the fact happened. The server keeps it unless it is more than ten minutes ahead of the server's clock, more than thirty days behind it, or from before the device was paired. A fact is never refused for its stamp: one the server does not believe, cannot read or was not given is stamped as the server takes it, and flagged on what it dates — the order, the shift, the drawer or the shelf.

idempotency_keyItemIdempotencyKey

Required
A key for one item in a batch, minted by the client when it queues the item and reused on every attempt to send it. The item, not the request, is the unit of work: a retried batch returns the stored result for every item already applied under its key. A fresh key per attempt defeats the whole mechanism.
Scoped per merchant, so keys need only be unique within a merchant's own traffic.
16–255 chars

shiftShiftWrite

Required
A shift as a client writes it: an open one to clock somebody in, or the same record written once more as closed when they clock out. The device supplies the id, so submitting the same shift twice — a retried batch after a lost response — converges on one record rather than opening a second shift. The merchant, the version and the timestamps are the server's, stamped on the record it holds, and are never demanded of or accepted from a client.

idstring · uuid

Required
UUIDv7, minted by the device.

breaksarray of ShiftBreak

Every break the till recorded on the shift, earliest first. A break is its own row keyed by the id the device minted, so a second break is appended rather than overwriting the first.

idstring · uuid

Required
UUIDv7, minted by the device.

ended_atstring · date-time

Nullable
When the break ended, or null while the member is still on it.

started_atstring · date-time

Required
When the break started, as the device saw it.

clock_in_atstring · date-time

Required
When the staff member clocked in, as the device saw it. Provided for reporting and display; the server stamps its own receipt time, because a till that has been off for a week comes back with a clock hours out.

clock_out_atstring · date-time

Nullable
When the staff member clocked out, or null while the shift is open.

device_idstring · uuid

Required
The till the staff member worked on.

location_idstring · uuid

Required
The location the staff member worked at.

member_idstring · uuid

Required
The staff member (a user on this merchant's roster).

statusstring · enum

Required
An open shift is in progress; a closed one has a clock-out time. The two are stated together so a shift can never be recorded in a state nobody expects.
openclosed

versioninteger · int64
The version of the shift this write was made from, as the server last reported it. Required to write a shift the server already holds (closing one), and refused as 412 when somebody else has written it since. Omitted to open a shift the server has never seen.
≥ 1
Responses

200
The batch was processed. results says what happened to each item.

BatchResponse · application/json

resultsarray of BatchResult

Required

idstring · uuid
The resource the item created or changed. Absent when it failed.

idempotency_keystring

Required
The item's key, echoed so a result can be matched by key as well as position.

problemProblem

Nullable
Why the item failed, as an RFC 9457 problem. A 422 means the item is malformed and will never succeed — drop it and show it to staff rather than retrying for ever. A 409 or a 5xx means try again later.

typestring · uri

Required
A stable URI identifying the problem kind. This is the field to branch on.
default about:blank

api_versionstring
Present on an api-version-retired or api-version-unknown refusal: the API-Version this server speaks (docs/decisions/0011).

detailstring
A human-readable explanation specific to this occurrence. Safe to show to a developer; never contains internal state, SQL, or stack traces.

instancestring · uri-reference
A URI reference identifying the specific occurrence.

invalid_paramsarray of InvalidParam

Present on 422 responses. Lists every field that failed validation, rather than only the first, so a client can highlight an entire form in one pass.

codestring
Stable machine-readable code for this failure, for clients that localise their own messages rather than showing reason.

pointerstring

Required
RFC 6901 JSON Pointer to the offending value within the request body. A pointer rather than a field name so that failures nested inside arrays — the third line item of an order — are addressable at all.

reasonstring

Required
Why this value was rejected, in human-readable form.

refusalsarray of Location refusal

Present on 409 responses to a withdrawal refused by the state it depends on (deleting a location with tills still assigned, open orders, …). Lists every reason at once, each with how much stands in the way, so a client can say what to put right and link to it rather than walking a person through one refusal after another.

kindstring

Required
A stable refusal kind — devices, open_orders, drawer_sessions, bookings or stock — that a client links to the screen that puts it right. Branch on this field, never on the surrounding prose.

countinteger

Required
How many things stand in the way of the withdrawal, so a client can repeat the number rather than re-read prose.
≥ 1

statusinteger

Required
The HTTP status code, repeated here so the body is self-contained.
100–599

titlestring

Required
A short, human-readable summary of the problem kind.

trace_idstring
The OpenTelemetry trace id for this request. Quote it in a support ticket and the whole request can be pulled up.

statusstring · enum

Required
created — the item made a new resource. updated — it changed an existing one.
unchanged — this key was already applied and the original outcome stands. A success, not an error: it is what a client retrying a batch it was unsure landed should expect, and it clears the item from its queue exactly as created does.
failed — the item was refused, and nothing else in the batch was affected. See problem.
createdupdatedunchangedfailed

versioninteger · int64
The resource's version after the item. Absent when it failed.

400
The request could not be parsed. Malformed JSON, a bad query parameter, or a header that failed to decode, among them an API-Version later than the server speaks or not a date (api-version-unknown, with the server's own in api_version).
Distinct from 422: a 400 never reached validation, so invalid_params is absent. Retrying without changing the request will fail again, except that a request refused for its API-Version goes once the server is updated.

401
No credentials, or credentials that could not be verified — missing bearer token, malformed JWT, expired token, or a signature that failed against the issuer's JWKS.
Refresh the token and retry once. Repeated 401 after a refresh means the device needs to re-enrol.

403
Authenticated, but not permitted. The token is valid and its merchant was resolved, but the caller's role does not allow this operation, or the target belongs to a different merchant.
Cross-tenant access is reported as 403 on a resource the caller may not see, and as 404 where even confirming existence would leak information. Retrying will not help.

410
The request names an API-Version this server no longer serves (docs/decisions/0011). Nothing in it was read. api_version names the version the server speaks: the client is behind, and sends the request again once it is updated.

415
The request Content-Type is not supported. This API accepts application/json on all mutations.

422
The request parsed but failed validation.
invalid_params lists every failing field with a JSON Pointer, not just the first, so a client can mark up a whole form in one pass rather than making the user fix errors one round trip at a time.
Also returned when an Idempotency-Key is replayed with a different body, and when device-computed order totals disagree with the server's recomputation.

429
Rate limit exceeded. Honour Retry-After rather than applying your own backoff.
A fleet of tills coming back online together after an outage is the realistic cause, which is exactly when uncoordinated client-side retry turns a brief outage into a sustained one. The limit is per process, and per site for what records trade there — a request spends its site's budget, and a till's own smaller one inside it — and per (client, merchant) for everything else; no RateLimit field is sent, so this response and its Retry-After are the whole of the contract.

500
Something failed on our side. trace_id identifies the request in our tracing — quote it in a support ticket.
The body never carries internal detail: no SQL, no stack traces, no upstream error strings. Safe to retry with the same Idempotency-Key.

503
Temporarily unable to serve the request — a dependency is down or the service is shedding load.
Retry with the same Idempotency-Key after Retry-After. This is always safe: a request that did take effect before the failure will be recognised as a replay.
Request
curl -X POST 'https://api.tenvelo.com/v1/shifts/batch-upsert' \ -H "Authorization: Bearer $TOKEN" \ -H 'Content-Type: application/json' \ -d '{ "items": [ { "hlc": "117356101632000000", "idempotency_key": "01J8ZK3QF7X2N5V9C4B1A6D8E0", "shift": { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "breaks": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "ended_at": "2026-09-11T09:30:00Z", "started_at": "2026-09-11T09:30:00Z" } ], "clock_in_at": "2026-09-11T09:30:00Z", "clock_out_at": "2026-09-11T09:30:00Z", "device_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "location_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "member_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "status": "open" }, "version": 1 } ] }'
Response
{ "results": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "idempotency_key": "string", "problem": { "type": "https://api.tenvelo.com/problems/version-conflict", "api_version": "2026-10-10", "detail": "The product has been modified since version 7 was read.", "instance": "/v1/products/0195f8c7-4a1e-7c3b-9f22-8d4e6a1b2c3d", "invalid_params": [ { "code": "minimum", "pointer": "/line_items/0/quantity", "reason": "must be greater than or equal to 1" } ], "refusals": [ { "kind": "devices", "count": 3 } ], "status": 412, "title": "Version conflict", "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736" }, "status": "created", "version": 0 } ] }
GET/v1/shifts/{id}

Get a shift

No. getShiftAuth pos:shifts:read
Returns a single shift.
Parameters

idpath · string · uuid
Required
UUIDv7 of the resource.
For resources a device can originate — orders, and their line items — this id is minted by the client before the record is ever synced, which is what makes an offline create idempotent.
Responses

200
The shift.

Shift · application/json

idstring · uuid

Required
UUIDv7, minted by the device.

breaksarray of ShiftBreak

Every break the till recorded on the shift, earliest first. A break is its own row keyed by the id the device minted, so a second break is appended rather than overwriting the first.

idstring · uuid

Required
UUIDv7, minted by the device.

ended_atstring · date-time

Nullable
When the break ended, or null while the member is still on it.

shift_idstring · uuid

Read only
The shift the break belongs to.

started_atstring · date-time

Required
When the break started, as the device saw it.

clock_in_atstring · date-time

Required
When the staff member clocked in, as the device saw it. Provided for reporting and display; the server stamps its own receipt time, because a till that has been off for a week comes back with a clock hours out.

clock_out_atstring · date-time

Nullable
When the staff member clocked out, or null while the shift is open.

created_atTimestamp

RequiredRead only
Server-assigned RFC 3339 timestamp, always UTC.
Server-assigned because device clocks drift and cannot be trusted for ordering — a till that has been powered off for a week may come back with a clock hours out. Where the device's own view of time matters it is carried separately in client_created_at.

device_idstring · uuid

Required
The till the staff member worked on.

location_idstring · uuid

Required
The location the staff member worked at.

member_idstring · uuid

Required
The staff member (a user on this merchant's roster).

merchant_idstring · uuid

RequiredRead only

statusstring · enum

Required
An open shift is in progress; a closed one has a clock-out time. The two are stated together so a shift can never be recorded in a state nobody expects.
openclosed

updated_atTimestamp

RequiredRead only
Server-assigned RFC 3339 timestamp, always UTC.
Server-assigned because device clocks drift and cannot be trusted for ordering — a till that has been powered off for a week may come back with a clock hours out. Where the device's own view of time matters it is carried separately in client_created_at.

versionVersion

RequiredRead only
Optimistic concurrency version, raised by the server on every write. A version is never lower than one already returned for the resource, though it may rise by more than one.
Returned in the ETag response header as well as in the body. Send it back in If-Match on an update and the write is rejected with 412 if anyone else has written since — which is what stops two tills silently overwriting each other's edit to the same product when both come back online at once.
≥ 1

400
The request could not be parsed. Malformed JSON, a bad query parameter, or a header that failed to decode, among them an API-Version later than the server speaks or not a date (api-version-unknown, with the server's own in api_version).
Distinct from 422: a 400 never reached validation, so invalid_params is absent. Retrying without changing the request will fail again, except that a request refused for its API-Version goes once the server is updated.

401
No credentials, or credentials that could not be verified — missing bearer token, malformed JWT, expired token, or a signature that failed against the issuer's JWKS.
Refresh the token and retry once. Repeated 401 after a refresh means the device needs to re-enrol.

403
Authenticated, but not permitted. The token is valid and its merchant was resolved, but the caller's role does not allow this operation, or the target belongs to a different merchant.
Cross-tenant access is reported as 403 on a resource the caller may not see, and as 404 where even confirming existence would leak information. Retrying will not help.

404
No such resource, or none visible to this caller.
Also returned instead of 403 where acknowledging existence would itself leak information — so a 404 does not prove the id is unused globally, only that it is not yours.

410
The request names an API-Version this server no longer serves (docs/decisions/0011). Nothing in it was read. api_version names the version the server speaks: the client is behind, and sends the request again once it is updated.

429
Rate limit exceeded. Honour Retry-After rather than applying your own backoff.
A fleet of tills coming back online together after an outage is the realistic cause, which is exactly when uncoordinated client-side retry turns a brief outage into a sustained one. The limit is per process, and per site for what records trade there — a request spends its site's budget, and a till's own smaller one inside it — and per (client, merchant) for everything else; no RateLimit field is sent, so this response and its Retry-After are the whole of the contract.

500
Something failed on our side. trace_id identifies the request in our tracing — quote it in a support ticket.
The body never carries internal detail: no SQL, no stack traces, no upstream error strings. Safe to retry with the same Idempotency-Key.

503
Temporarily unable to serve the request — a dependency is down or the service is shedding load.
Retry with the same Idempotency-Key after Retry-After. This is always safe: a request that did take effect before the failure will be recognised as a replay.
Request
curl -X GET 'https://api.tenvelo.com/v1/shifts/0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b' \ -H "Authorization: Bearer $TOKEN"
Response
{ "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "breaks": [ { "id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "ended_at": "2026-09-11T09:30:00Z", "shift_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "started_at": "2026-09-11T09:30:00Z" } ], "clock_in_at": "2026-09-11T09:30:00Z", "clock_out_at": "2026-09-11T09:30:00Z", "created_at": "2026-09-08T09:41:12Z", "device_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "location_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "member_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "merchant_id": "0192f1e4-7c3a-7b2e-9f10-5d6c7e8f9a0b", "status": "open", "updated_at": "2026-09-08T09:41:12Z", "version": 7 }

Parameters

Responses

Parameters

Responses

Request body application/json · ShiftBatchUpsertRequest

Responses

Parameters

Responses