How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Afero Cloud Devices API

The Afero Cloud Devices API lists the devices linked to an Afero account and, via the expansions query parameter, returns device state (available, visible, connected, connectable, linked, RSSI, location), system and partner device tags, or the raw device attribute values. It also executes asynchronous attribute_read and attribute_write actions against a device by attribute ID with hexadecimal little-endian payloads, and updates a device friendly name.

Afero Cloud Devices API is one of 4 APIs that Afero publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Devices, Device Management, Internet of Things, and Telemetry. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.afero.io.

4 operations 4 paths 10 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.afero.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Afero Cloud Devices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — The OAuth 2.0 access token returned by POST /oauth/token, sent as Authorization: Bearer . Tokens expire (approximately four hours per the Afero docs).

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Devices 4

Afero devices on an account: listing, real-time state, attribute actions and naming.

GET
/v1/accounts/{accountId}/devices
List current devices and state information
listDevices 2 params → 200401403404
GET
/v1/accounts/{accountId}/devices/{deviceId}
Get a single device and its state information
getDevice 3 params → 200401403404
POST
/v1/accounts/{accountId}/devices/{deviceId}/actions
Execute an action on a device
executeDeviceAction 2 params body → 200401403404
PUT
/v1/accounts/{accountId}/devices/{deviceId}/friendlyName
Update the friendly name of a device
updateDeviceFriendlyName 2 params body → 200401403404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Device (13 properties), DeviceState (10 properties), Error (6 properties), DeviceActionResult (5 properties). Each schema is shown below with its type and property counts.

DeviceTag
object
Returned when the tags expansion is requested.
4 properties
Error
object
The Afero Cloud API error envelope, observed live on api.afero.io (2026-08-02).
6 properties
DeviceState
object
Returned when the state expansion is requested.
10 properties
Device
object
13 properties
DeviceLocation
object
3 properties
ActionSource
object
4 properties
FriendlyName
object
1 property 1 required
DeviceAction
object
3 properties 2 required
DeviceAttribute
object
Returned when the attributes expansion is requested.
3 properties
DeviceActionResult
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

afero-devices-api-openapi.yml Raw ↑

Other APIs Afero publishes across the network.

Afero Cloud Authentication API
Afero Cloud Users API
Afero Cloud OTA Firmware API
Where this information came from

This is an independent, third-party profile of Afero Cloud Devices API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.