Skip to main content
POST
Lock series to mobile device

Overview

Locking a series binds it to the mobile device that issued the call (identified by the device_id stored on its user_session). Once locked:
  • Only that device can issue invoices against the series — online or via pre-reserved numbers when offline.
  • Web/API-key callers attempting to POST /invoices with a locked series_id receive a series_locked_to_device error.
  • The locked device can call POST /invoice-series/{id}/reserve-numbers to pre-allocate numbers for offline use.
This prevents race conditions on the invoice number counter when a mobile device is offline and a web user is also trying to emit invoices on the same series.
Requires a mobile JWT session (issued by /auth/login). The JWT’s backing user_session must have a non-empty device_id — re-authenticate from the app if device_id_missing is returned.

Response

object
required
Non-null once the series is locked.
boolean
Always true after a successful lock.

Authorizations

Authorization
string
header
required

Use your API key (sk_live_xxx or sk_test_xxx)

Path Parameters

id
string
required

Response

Series locked

success
boolean
data
object
meta
object