Skip to main content
POST
/
devices
/
{id}
/
unbind
curl -X POST https://api.bota.dev/v1/devices/dev_abc123/unbind \
  -H "Authorization: Bearer sk_live_..."
{
  "id": "dev_abc123",
  "serial_number": "SN-2025-001234",
  "device_type": "bota_pin_v1",
  "firmware_version": "1.2.0",
  "status": "unbound",
  "end_user_id": null,
  "metadata": null,
  "created_at": "2025-01-15T10:30:00Z",
  "bound_at": null
}
Unbind a device from its current end user, making it available for reassignment. This is a no-op if the device is not currently bound.

Authentication

Requires an API key with devices:write scope.
curl -X POST https://api.bota.dev/v1/devices/dev_abc123/unbind \
  -H "Authorization: Bearer sk_live_..."

Path Parameters

id
string
required
The device’s unique identifier (e.g., dev_abc123).

Response

Returns the device object with status set to unbound.
{
  "id": "dev_abc123",
  "serial_number": "SN-2025-001234",
  "device_type": "bota_pin_v1",
  "firmware_version": "1.2.0",
  "status": "unbound",
  "end_user_id": null,
  "metadata": null,
  "created_at": "2025-01-15T10:30:00Z",
  "bound_at": null
}

Response Fields

FieldTypeDescription
idstringDevice identifier (dev_*)
serial_numberstringPhysical serial number
modelstringDevice model (bota_pin or bota_note)
firmware_versionstring | nullCurrent firmware version
statusstringunbound or bound
end_user_idstring | nullBound end user (eu_*), null if unbound
battery_percentinteger | nullBattery level (0-100), null if no heartbeat received
storage_used_mbinteger | nullStorage used in MB
storage_total_mbinteger | nullTotal storage capacity in MB
signal_strength_dbminteger | nullSignal strength in dBm
last_heartbeat_atstring | nullLast heartbeat timestamp (ISO 8601)
recording_stateobject | nullCurrent recording state (device_state, pending_recordings, flags, connection_type[])
metadataobjectCustom key-value metadata
created_atstringCreation timestamp (ISO 8601)
updated_atstringLast update timestamp (ISO 8601)
Unbinding a device does not affect existing recordings. Recordings remain associated with the end user who was bound at the time of recording.