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

# Remove a user

> Delete a user by its user ID and the ID of the user's organization.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json delete /api/partners/v2.0/org/{org_id}/users/{user_id}
openapi: 3.1.0
info:
  title: Podero Partner API
  version: '2.0'
  description: >-
    This API provides a unified interaction point for Podero's partner
    companies.


    The goal of this API is to give partners easily integratable endpoints that
    don't require extensive software

    development. For this reason, the endpoints focus around user and device
    management, setting of preferences

    and high level device controls.


    While direct control of devices is implemented for special use cases such as
    pause power, we abstract away low level

    direct device steering so developers and partners can focus on delivering
    maximum value to end users.


    ## Authentication


    Send an OAuth2 access token in the `Authorization: Bearer <access_token>`
    header of each request.

    A token request must have a JSON body. The token endpoints do not read a
    form-encoded body.


    Server-to-server integrations use the client credentials grant:


    ```http

    POST /oauth2/token/

    Authorization: Basic base64(<client_id>:<client_secret>)

    Content-Type: application/json


    {"grant_type": "client_credentials"}

    ```


    The response does not contain a refresh token. The access token expires
    after `expires_in` seconds (one hour).

    To renew it, send the same request again. Use one token for all requests
    until shortly before it expires.

    Do not request a new token for each request. If a request returns `401`, get
    one new token and send the request

    again once. If it returns `401` again, the token is valid but the
    application has no access to that resource,

    and a new token does not change that.


    Apps where a person signs in use the password grant at `POST
    /api/partners/v2.0/auth/token`, and renew the

    session with the `refresh_token` grant at the same endpoint.
  termsOfService: https://www.podero.com/terms-and-conditions
servers: []
security: []
paths:
  /api/partners/v2.0/org/{org_id}/users/{user_id}:
    delete:
      tags:
        - Users
      summary: Remove a user
      description: Delete a user by its user ID and the ID of the user's organization.
      operationId: >-
        integrations_api_api_v2_organizations_users_router_delete_organization_user
      parameters:
        - in: path
          name: org_id
          schema:
            description: The organization ID of the user's organization
            format: uuid
            title: Org Id
            type: string
          required: true
          description: The organization ID of the user's organization
        - in: path
          name: user_id
          schema:
            description: The user ID of the user to be deleted
            format: uuid
            title: User Id
            type: string
          required: true
          description: The user ID of the user to be deleted
        - in: query
          name: soft_delete
          schema:
            default: false
            description: >-
              Sets when Podero anonymises the personal data. false: within one
              day after the offboarding completes. true: 30 days after the
              delete. Every delete starts the offboarding: Podero revokes its
              access at the manufacturer where the manufacturer supports it, and
              deletes the stored credentials. Podero keeps the record and its
              measurements without personal data, except the user's external
              user ID: it stays for 638 days after the user's delete, so that
              historical data can be matched to your records. It goes with the
              other personal data when the user is deleted with false, or when
              the ID is an e-mail address. For a user, the setting also applies
              to the user's devices. false also applies to a user or device that
              is already deleted.
            title: Soft Delete
            type: boolean
          required: false
          description: >-
            Sets when Podero anonymises the personal data. false: within one day
            after the offboarding completes. true: 30 days after the delete.
            Every delete starts the offboarding: Podero revokes its access at
            the manufacturer where the manufacturer supports it, and deletes the
            stored credentials. Podero keeps the record and its measurements
            without personal data, except the user's external user ID: it stays
            for 638 days after the user's delete, so that historical data can be
            matched to your records. It goes with the other personal data when
            the user is deleted with false, or when the ID is an e-mail address.
            For a user, the setting also applies to the user's devices. false
            also applies to a user or device that is already deleted.
      responses:
        '200':
          description: OK
      security:
        - OAuth2: []
components:
  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        password:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}
        clientCredentials:
          tokenUrl: /oauth2/token/
          scopes: {}

````

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