AMETEK Device Identity API

openapi: 3.2.0
info:
  title: AMETEK Powervar iSite PRO REST Device Identity API
  version: v1
  summary: Read-only REST API embedded in the AMETEK Powervar iSite PRO network management card.
  description: The REST API published by AMETEK Powervar for the iSite PRO network management adapter, a card fitted to Powervar UPS systems for secure remote monitoring.
  contact:
    name: AMETEK Powervar
    url: https://www.powervar.com
  x-source-pdf: https://www.powervar.com/-/media/ametekpowervar/pdf/products/connectivity-solutions/isite-pro/user-manuals/a55-00202-rev-b-isite-pro-rest-api-definition.pdf
servers:
- url: http://{device_host}:{port}/api/v1
  description: The iSite PRO adapter itself. `device_host` is the adapter's own IP address or mDNS hostname (the document's worked examples use an adapter reachable on port 8080 and a hostname of the form isitepro-<serial>). HTTPS is supported; HTTP is the factory default.
  variables:
    device_host:
      default: isitepro.local
      description: IP address or mDNS hostname of the customer's iSite PRO adapter.
    port:
      default: '80'
      description: HTTP listener port reported by the adapter's own httpd.port field. Examples in the definition use 8080.
security:
- basicAuth: []
- sessionToken: []
tags:
- name: Device Identity
  description: Identify the adapter itself — model, serial, firmware, network interfaces and httpd state.
paths:
  /whoAreYou:
    get:
      operationId: getWhoAreYou
      summary: Identify the adapter
      description: 'Returns the adapter''s own identity and network configuration — model, serial number, manufacturer, current UTC time, firmware version, hostname, every Ethernet interface with its addressing, and the state of the embedded HTTP server.


        Note the case difference published in the definition: the URL is documented as `/api/v1/whoAreYou` while the worked example request line reads `GET /api/v1/WhoAreYou`. Both spellings appear in AMETEK Powervar''s own document; this spec carries the URL as published in the URL field.'
      tags:
      - Device Identity
      responses:
        '200':
          description: Adapter identity and network state.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WhoAreYou'
components:
  schemas:
    WhoAreYou:
      type: object
      title: WhoAreYou
      description: Adapter identity and network state. Field set taken verbatim from the published example response body.
      properties:
        objType:
          type: string
          description: Object discriminator; "whoAreYou" in the published example.
        model:
          type: string
          description: Adapter model, e.g. "iSitePro".
        serial:
          type: string
          description: Adapter serial number.
        manufacturer:
          type: string
          description: Manufacturer; "AMETEK" in the published example.
        time:
          type: string
          format: date-time
          description: Adapter's current UTC time.
        firmware:
          type: string
          description: Adapter firmware version.
        hostname:
          type: string
          description: Adapter hostname, of the form isitepro-<serial>.
        ethInterfaces:
          type: array
          description: Every Ethernet interface on the adapter.
          items:
            $ref: '#/components/schemas/EthInterface'
        httpd:
          $ref: '#/components/schemas/HttpdState'
    EthInterface:
      type: object
      title: EthInterface
      properties:
        mac:
          type: string
          description: Interface MAC address.
        ifname:
          type: string
          description: Interface name, e.g. "eth0".
        dns:
          type: array
          items:
            type: string
          description: Configured DNS resolvers.
        addr:
          type: string
          description: Assigned IPv4 address.
        dhcp:
          type: boolean
          description: Whether the address was obtained by DHCP.
        mask:
          type: string
          description: Subnet mask.
        gw:
          type: string
          description: Default gateway.
    HttpdState:
      type: object
      title: HttpdState
      description: State of the adapter's embedded HTTP server.
      properties:
        enabled:
          type: boolean
          description: Whether the embedded HTTP server is enabled.
        ssl:
          type: boolean
          description: Whether TLS is enabled. HTTP (ssl false) is the factory default.
        status:
          type: string
          description: Server status, e.g. "OK".
        port:
          type: integer
          description: Listener port.
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: HTTP Basic Authentication, as published. Authentication is required for access to all API features. Credentials are the adapter's own local administrative credentials.
    sessionToken:
      type: apiKey
      in: header
      name: x-auth-token
      description: Web session token issued by the adapter's own web interface and presented in the `x-auth-token` header, as published.
x-authored-by: API Evangelist
x-generated-from: documentation
x-modeled-from: https://www.powervar.com/-/media/ametekpowervar/pdf/products/connectivity-solutions/isite-pro/user-manuals/a55-00202-rev-b-isite-pro-rest-api-definition.pdf
x-provenance:
  method: generated
  generated: '2026-09-02'
  source_document: A55-00202 REV B — "Rest API Definition", AMETEK Powervar, Inc., dated 03/10/2023
  source_url: https://www.powervar.com/-/media/ametekpowervar/pdf/products/connectivity-solutions/isite-pro/user-manuals/a55-00202-rev-b-isite-pro-rest-api-definition.pdf
  http_status: 200
  note: Transcribed by API Evangelist from AMETEK Powervar's own published REST API definition PDF. AMETEK Powervar publishes no OpenAPI of its own. Every path, method, header, status code and response field below appears verbatim in that document; nothing has been inferred or invented. Response schemas are typed from the document's worked example bodies. Undocumented behaviour (error responses, rate limits) is deliberately ABSENT rather than guessed.