> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plaud.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Unbind Device

> Removes the device/owner association in the Plaud registry. Unbinding an already-unbound device is idempotent, so multiple calls have no side effects.

Plaud devices can only be bound to one application at a time. Unbind over both cloud and BLE — call this endpoint and call `depair(clear: true)` on the Embedded SDK — so the cloud and local bind state stay in sync.



## OpenAPI

````yaml /openapi/binding.json post /open/partner/sdk/unbind
openapi: 3.0.4
info:
  title: Device Binding APIs
  description: >-
    APIs that track device state remotely. Binding a Plaud device involves two
    steps:

    1. **Cloud bind**: registers the device/owner association in the Plaud
    registry so you can track Connected Device state remotely

    2. **Local device bind**: triggered over BLE by the Embedded SDK, which
    verifies and generates the key pair on-device
  version: 0.0.1
servers:
  - url: https://platform-us.plaud.ai/developer/api
    description: US partner endpoint
  - url: https://platform-jp.plaud.ai/developer/api
    description: Japan partner endpoint
security:
  - bearerAuth: []
paths:
  /open/partner/sdk/unbind:
    post:
      tags:
        - Device Binding API
      summary: Unbind Device
      description: >-
        Removes the device/owner association in the Plaud registry. Unbinding an
        already-unbound device is idempotent, so multiple calls have no side
        effects.


        Plaud devices can only be bound to one application at a time. Unbind
        over both cloud and BLE — call this endpoint and call `depair(clear:
        true)` on the Embedded SDK — so the cloud and local bind state stay in
        sync.
      operationId: unbindDevice
      parameters:
        - $ref: '#/components/parameters/jsonContentType'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeviceRef'
            example:
              type: notepro
              sn: '8810000000000001'
      responses:
        '200':
          description: Device unbound
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BindResponse'
              example:
                type: notepro
                sn: '8810000000000001'
                is_bind: false
        '404':
          description: Unknown device — the serial number is not in the Plaud registry.
components:
  parameters:
    jsonContentType:
      in: header
      name: Content-Type
      schema:
        type: string
        default: application/json
      required: true
  schemas:
    DeviceRef:
      type: object
      required:
        - type
        - sn
      properties:
        type:
          type: string
          description: >-
            Device type string derived from the SN prefix (`881` → `notepro`,
            `882` → `notepins`).
          example: notepro
        sn:
          type: string
          description: Device serial number.
          example: '8810000000000001'
    BindResponse:
      type: object
      properties:
        type:
          type: string
          description: Device type string.
          example: notepro
        sn:
          type: string
          description: Device serial number.
          example: '8810000000000001'
        is_bind:
          type: boolean
          description: Remote binding state of the device after the call.
          example: true
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Bearer authentication using a **User Token**. See the [Authentication
        API reference](/plaud-embedded/auth-api-overview) for how to mint one.

````