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

# Unregister this phone from push

> Forget this key's token - when the app deletes its key, or the
operator turns notifications off. Another key's token stays.



## OpenAPI

````yaml /setup/internal-openapi.json delete /v1/mobile/push/token
openapi: 3.1.0
info:
  title: n:lead Scheduling Bridge — Internal API
  version: 0.4.0
  description: >-
    Internal API of the n:lead scheduling bridge: the process endpoints that
    drive the day-ahead pipeline (aggregate, publish the open position, submit
    schedules, generate forecasts, orchestrate), the operator console endpoints,
    and the read-only operator-app endpoints under /v1/mobile. The process and
    console endpoints require the process API key, /v1/mobile a device key of
    the mobile scope; not for customer use.
servers:
  - url: https://{host}
    description: Deployed service
    variables:
      host:
        default: api.energy.nlead.ch
        description: >-
          The service hostname - n:lead provides it (see the Base URL on the API
          introduction page)
  - url: http://localhost:8000
    description: Local development
security: []
paths:
  /v1/mobile/push/token:
    delete:
      tags:
        - mobile
      summary: Unregister this phone from push
      description: |-
        Forget this key's token - when the app deletes its key, or the
        operator turns notifications off. Another key's token stays.
      operationId: delete_push_token_v1_mobile_push_token_delete
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PushToken'
        required: true
      responses:
        '204':
          description: Successful Response
        '401':
          description: Missing or unknown device key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MobileError'
        '403':
          description: A valid key of another scope - only device keys open /v1/mobile.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MobileError'
        '422':
          description: Not a device token, or the key holds three already.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MobileError'
        '429':
          description: Rate limit exceeded; wait the seconds in `Retry-After`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MobileError'
        '500':
          description: Unexpected server error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MobileError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    PushToken:
      properties:
        token:
          type: string
          pattern: ^[0-9a-f]{64,200}$
          title: Token
        language:
          type: string
          enum:
            - de
            - en
          title: Language
          description: >-
            the app's language, which the notifications follow; sent again when
            it changes
          default: en
      additionalProperties: false
      type: object
      required:
        - token
      title: PushToken
      description: The phone's APNs device token, as lower-case hex.
    MobileError:
      properties:
        error:
          type: string
          enum:
            - unauthorized
            - forbidden
            - invalid_request
            - rate_limited
            - upstream_unavailable
            - internal
          title: Error
      additionalProperties: false
      type: object
      required:
        - error
      title: MobileError
      description: |-
        Every error under /v1/mobile: a code, nothing else - no detail text,
        no echo of the request.
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.