Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

EcoFlow Devices API

Device discovery and binding

EcoFlow Devices API is one of 3 APIs that EcoFlow publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 2 base URLs: https://api.ecoflow.com, https://api-e.ecoflow.com.

1 operations 1 paths 4 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.ecoflow.com
Authentication
API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 4

EcoFlow Devices API declares 4 security schemes for authenticating requests. An API key is passed in the header as accessKey (accessKey). An API key is passed in the header as nonce (nonce). An API key is passed in the header as timestamp (timestamp). An API key is passed in the header as sign (sign). By default, every request must be authenticated.

  • accessKey — Access key issued in the EcoFlow developer console.
  • nonce — Random nonce (typically a 6-digit number) regenerated per request.
  • timestamp — Unix timestamp in milliseconds at request time.
  • sign — HMAC-SHA256 signature (hex) over the ASCII-sorted request parameters concatenated with accessKey, nonce and timestamp, keyed by the secretKey.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Devices 1

Device discovery and binding

GET
/iot-open/sign/device/list
List bound devices
getDeviceList → 200401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Device (3 properties), Envelope (2 properties). Each schema is shown below with its type and property counts.

Device
object
3 properties
Envelope
object
Standard EcoFlow response envelope.
2 properties 2 required
ErrorResponse
DeviceListResponse

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ecoflow-devices-api-openapi.yml Raw ↑

Other APIs EcoFlow publishes across the network.

EcoFlow MQTT API
EcoFlow Quota API