> ## 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.

# Resolve a Device to its owner and type

> Resolve a device uuid (from `GET /org/{org_id}/devices`) to its owner and type
without prior knowledge of either, so cockpit deep links can follow the existing
nested per-type detail route. Scoped to the org: a device in another org 404s.

Available only for "admin" users.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json get /api/partners/v2.0/org/{org_id}/devices/{device_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.
  termsOfService: https://www.podero.com/terms-and-conditions
servers: []
security: []
paths:
  /api/partners/v2.0/org/{org_id}/devices/{device_id}:
    get:
      tags:
        - Devices
      summary: Resolve a Device to its owner and type
      description: >-
        Resolve a device uuid (from `GET /org/{org_id}/devices`) to its owner
        and type

        without prior knowledge of either, so cockpit deep links can follow the
        existing

        nested per-type detail route. Scoped to the org: a device in another org
        404s.


        Available only for "admin" users.
      operationId: integrations_api_api_v2_organizations_devices_router_resolve_device
      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: device_id
          schema:
            description: The device ID to resolve
            format: uuid
            title: Device Id
            type: string
          required: true
          description: The device ID to resolve
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeviceResolutionOutput'
      security:
        - OAuth2: []
components:
  schemas:
    DeviceResolutionOutput:
      description: >-
        Thin resolver payload: enough to follow the nested per-type detail route

        (`/org/{o}/users/{owner_id}/<type>/{device_id}`) knowing only the device
        uuid.

        device_type is the DeviceType short_name (ev, inv, wb, hp_atw, hp_wtw,
        ...), null

        for a device with no device_model.
      properties:
        owner_id:
          format: uuid
          title: Owner Id
          type: string
        device_type:
          anyOf:
            - type: string
            - type: 'null'
          title: Device Type
      required:
        - owner_id
      title: DeviceResolutionOutput
      type: object
  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        password:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}
        clientCredentials:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}

````