Changelog

Stay up to date with the latest improvements, new features, and bug fixes across the Bota platform.

---

​

August 2026

​

2026-08-19

Bota One Device Integration Contract

• Documented pk_d delivery during bind and the nonce-bound BLE deprovision grant used by the released Bota One integration.
• Documented optional one-time cert delivery used by the demo mTLS integration, including secret-handling and compatibility requirements.
• Added the deprovision grant endpoint to the public API reference and clarified that deprovision is not factory reset.
• Corrected WiFi setup to match the current SDK/firmware contract and corrected already-unbound behavior to 400 Bad Request.

​

2026-08-12

Project-Scoped End User Lookup

• GET /v1/end-users accepts an exact external_id filter and returns zero or one end user in the standard collection response.
• External-ID lookup is scoped to the authenticated project. Empty results do not reveal whether an end user exists in another project.

​

2026-08-09

Lifetime Device Serial Identity

• Device serial numbers remain reserved after soft deletion; attempting to register the same serial as a new device returns 409 Conflict.
• Same-organization project moves preserve the existing dev_* identity rather than deleting and recreating the device.
• Registration now has a database concurrency guard so simultaneous requests cannot create duplicate device identities.

---

​

July 2026

​

2026-07-30

API Reference Contract Corrections

• Aligned recording, upload, transcription, summary, and webhook examples with the current /v1 backend contract.
• Corrected transcription creation to POST /v1/transcriptions and download URL generation to GET /v1/recordings/{id}/download-url.
• Marked dashboard-only or not-yet-mounted endpoints as unavailable in the public /v1 API.

​

2026-07-26

Authenticated Factory Reset Close-Loop

• POST /v1/devices/{id}/reset now returns 202 Accepted with a durable, idempotent factory_reset command.
• The device stays bound until it deletes every locally stored recording and acknowledges the exact command; only then does Bota unbind it, revoke its token, and clear device configuration.
• Cloud recordings, transcriptions, summaries, and manufacturing identity are preserved. Lost acknowledgement responses can be retried safely.
• Reset completion credentials and project-key finalization require devices:write; read-only command responses omit the credential.
• This entry covers the backend API contract. The physical wipe requires the compatible firmware and relay releases before it can complete.

​

2026-07-24

Webhook Signature Documentation Correction

• Corrected webhook verification examples to match the delivered v1=<digest> signature format.
• Documented that version 1 signs <timestamp>.<raw-request-body>, not the body alone.
• Added raw-body handling, constant-time comparison, and a five-minute timestamp tolerance to the Node.js and Python examples.

​

2026-07-18

Heartbeat Channel Control

• Device settings can independently enable or disable direct WiFi and cellular heartbeats without changing upload routing.
• Bluetooth heartbeat relay remains enabled and direct routing stays fixed as WiFi, then cellular.
• Disabling both direct paths requires a Bluetooth connection to re-enable one later.

​

2026-07-15

Project-Scoped Device Lookup

• GET /v1/devices now accepts an exact serial_number filter and returns zero or one device in the standard collection response.
• Serial-number lookup is scoped to the authenticated project. Empty results do not reveal whether a device exists in another project.
• POST /v1/devices remains create-only and returns 409 Conflict for duplicate serial numbers.

---

​

March 2026

​

2026-03-11

Auto-Processing & Hierarchical Configuration

• Auto-Transcription — Automatically transcribe recordings when upload completes. Configurable ASR provider per organization, project, end user, or device.
• Auto-Summary — Automatically generate summaries when transcription completes. Configurable LLM provider and template (general notes, sales call, clinical SOAP, legal memo).
• Hierarchical Configuration — New processing config section joins connection and upload. Set defaults at the organization level and override at project, end user, or device level with deep-merge inheritance.
• Config API Endpoints — GET/PUT/DELETE config endpoints available for all entity levels (organizations, projects, end users, devices).

See the Auto-Processing Guide and Hierarchical Configuration Guide for details.

---

​

January 2025

​

2025-01-15

API v1 General Availability We’re excited to announce the general availability of the Bota API v1. This release includes:

• End User Management — Create, list, and manage EndUsers with external_id mapping
• Device Management — Register devices, bind to EndUsers, and track fleet status
• Recording Pipeline — Create recordings, upload audio via pre-signed URLs, and track processing status
• Transcription — Async transcription with speaker diarization and timestamps
• Summarization — AI-powered summary generation from transcripts
• Webhooks — Real-time notifications for all processing events

​

2025-01-10

Documentation Site Launch

• Launched docs.bota.dev with comprehensive API reference
• Added quickstart guide for rapid integration
• Published hardware guides for Bota Pin and Bota Note

---

​

Versioning Policy

The Bota API uses date-based versioning. The current version is 2025-01-15. When we make breaking changes, we:

1. Release a new API version
2. Provide a migration guide
3. Support the previous version for at least 12 months
4. Send deprecation notices via email and webhooks

See API Versioning for details on version headers and migration strategies.

---

​

Deprecations

No deprecations at this time.

---

​

SDK Releases

---

​

Stay Updated