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

Tuya Devices API

Query and manage IoT device information

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

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 3 base URLs: https://openapi.tuyaus.com, https://openapi.tuyaeu.com, https://openapi.tuyain.com.

6 operations 4 paths 6 schemas 1 DELETE4 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://openapi.tuyaus.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Tuya Devices API declares 1 security scheme for authenticating requests. An API key is passed in the header as client_id (tuyaApiKey). By default, every request must be authenticated.

  • tuyaApiKey — Tuya API uses HMAC-SHA256 signed requests. Include your Access ID as the clientid header and provide a sign header computed from your Access ID, Access Secret,…

Paths & Operations 6

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

Devices 6

Query and manage IoT device information

GET
/v1.0/devices/{device_id}
Get Device Details
getDevice 1 param → 200401404
PUT
/v1.0/devices/{device_id}
Update Device Name
updateDevice 1 param body → 200401404
DELETE
/v1.0/devices/{device_id}
Remove Device
removeDevice 1 param → 200401404
GET
/v1.0/devices
List Devices
listDevices 4 params → 200401
GET
/v1.0/users/{uid}/devices
List User Devices
listUserDevices 3 params → 200401404
GET
/v1.0/devices/factory-infos
Get Device Factory Information
getDeviceFactoryInfos 1 param → 200401

Schemas 6

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

FactoryInfoResponse
object
3 properties
SuccessResponse
object
3 properties
DataPoint
object
2 properties
Device
object
17 properties
DeviceResponse
object
3 properties
DeviceListResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tuya-devices-api-openapi.yml Raw ↑

Other APIs Tuya publishes across the network.

Tuya Device Management API
Tuya Smart Home API
Tuya Authorization API
Tuya Industry API
Tuya Device Control API
Tuya Device Logs API
Tuya Device Users API
Tuya Sub Devices API
Where this information came from

This is an independent, third-party profile of Tuya 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.