Xcel Energy

Xcel Energy Time API

Current device time and time-zone configuration.

Documentation GitHub OpenAPI

Operations 1

GET /tm Get device time and time-zone parameters #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/xcel-energy-time-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Xcel Energy Smart Meter IEEE 2030.5 Time API
  summary: IEEE 2030.5 (SEP 2.0) REST API exposed by Itron Gen 5 Riva smart meters on the local network.
  description: IEEE 2030.5 / Smart Energy Profile 2.0 compliant API server built into Itron Gen 5 Riva smart meters deployed by Xcel Energy.
  version: '1.0'
  contact:
    name: Xcel Energy Developer Portal
    url: https://developer-apim.aws.xcelenergy.com/
  x-generated-from: documentation
  x-last-validated: '2026-05-03'
  x-standards:
  - IEEE 2030.5-2018
  - Smart Energy Profile 2.0
servers:
- url: https://{meterHost}
  description: Itron Gen 5 Riva smart meter on the local network (mTLS).
  variables:
    meterHost:
      default: 192.168.1.10
      description: Hostname or IP of the local meter device.
tags:
- name: Time
  description: Current device time and time-zone configuration.
paths:
  /tm:
    get:
      operationId: getTime
      summary: Get device time and time-zone parameters
      description: Returns the Time resource describing the current UTC time and the device time zone.
      tags:
      - Time
      security:
      - mtls: []
      responses:
        '200':
          description: Time resource.
          content:
            application/sep+xml:
              schema:
                $ref: '#/components/schemas/Time'
        '401':
          $ref: '#/components/responses/Unauthorized'
      x-microcks-operation:
        delay: 0
        dispatcher: FALLBACK
components:
  responses:
    Unauthorized:
      description: TLS authentication failed or the client certificate is not authorized.
  schemas:
    Resource:
      type: object
      description: Base IEEE 2030.5 Resource type that all resources inherit from.
      properties:
        href:
          type: string
          description: Stable URI of the resource.
    Time:
      allOf:
      - $ref: '#/components/schemas/Resource'
      - type: object
        properties:
          currentTime:
            type: integer
            description: Current time as epoch seconds.
          tzOffset:
            type: integer
            description: Offset of local time from UTC in seconds.
          dstOffset:
            type: integer
            description: DST offset from local standard time in seconds.
          dstStartTime:
            type: integer
          dstEndTime:
            type: integer
          quality:
            type: integer
            description: Time-source quality enumerated value.
          localTime:
            type: integer
  securitySchemes:
    mtls:
      type: mutualTLS
      description: 'IEEE 2030.5 requires mutual TLS authentication. Clients present a device certificate whose subject contains the LFDI/SFDI used to authorize access. Plain HTTP is not permitted.

        '