The app
Setup, control, sharing, and accounts for each user.
SetupControlSharingAccounts
Tuya Cloud API integration
Tuya Cloud API for Custom Apps and Backend Workflows
Turn device data into operations, automation, business integrations, and platform revenue — beyond what the customer app can do.
Real-time events 7 data centers Business workflows
Product architecture
Two layers. Two audiences. One connected product.
The app serves each customer. The platform helps your company operate across every device and user. The Cloud API backend is one layer of custom smart home app development — choose the right app path first.
Tuya Cloud API / platform
Operations, automation, integrations, and revenue across the installed base.
OperationsAutomationIntegrationsRevenue
What it unlocks
Where the platform creates value.
Value 01
Run operations and support without flying blind
See device status and recent activity across the installed base, so support can resolve issues faster.
Device APIs + real-time event messaging
Value 02
Connect the product to your business systems
Sync device and usage data with CRM, billing, warranty, maintenance, and partner tools.
Device, user, and data services
Value 03
Automate and alert on the server, not just in the app
Run scheduled checks, alerts, and cross-device rules — even when the app is closed.
Pulsar-based Message Queue
Value 04
Open higher-value, recurring business
Build subscriptions, premium features, or B2B portals on top of the installed base.
Recurring revenue models
Honest read
Fit first.
Not every product needs a platform. We test the B2B, subscription, or operational case before you invest.
The first decision
What belongs in the platform layer?
Separate customer app needs from company-wide workflows.
Rule of thumb
One user needs it: app. Your company needs it: platform.
Pair, control, and manage devices in the app
App SDK
YesCloud API
—Branded onboarding, rooms, sharing, user accounts
App SDK
YesCloud API
—Device status pushed to a server (not just the phone)
App SDK
—Cloud API
Yes — Message QueueSupport/ops view of devices across all users
App SDK
—Cloud API
Yes — device & data APIsServer-side automation, scheduled checks, alerts
App SDK
—Cloud API
YesSync device/usage data into CRM, billing, or partner systems
App SDK
—Cloud API
YesSubscriptions, premium tiers, or a B2B/B2C portal
App SDK
—Cloud API
Yes| Product capability | App SDK | Cloud API |
|---|---|---|
| Pair, control, and manage devices in the app | Yes | — |
| Branded onboarding, rooms, sharing, user accounts | Yes | — |
| Device status pushed to a server (not just the phone) | — | Yes — Message Queue |
| Support/ops view of devices across all users | — | Yes — device & data APIs |
| Server-side automation, scheduled checks, alerts | — | Yes |
| Sync device/usage data into CRM, billing, or partner systems | — | Yes |
| Subscriptions, premium tiers, or a B2B/B2C portal | — | Yes |
Technical foundation
The setup teams most often underestimate.
Three decisions, in order: authenticate, match the project region, then choose how events reach your backend.
01
Authenticate
Token and request signing
02
Match region
Project and endpoint
03
Stream events
Message Queue, not polling
01
Authentication
Sign every Tuya Cloud API request.
Request a token, then sign each call with HMAC-SHA256 and a 13-digit timestamp. Cloud and app authorization use different modes.
Client IDTokenSigned call
02
Data center
Use the endpoint where the devices live.
Each project belongs to one region. A mismatch can look like a permission or “no data” error.
Region
China
openapi.tuyacn.comApp account / devices in mainland China
Region
Western America
openapi.tuyaus.comThe Americas — and the default for unmapped countries
Region
Eastern America
openapi-ueaz.tuyaus.comProjects on the US-East center
Region
Central Europe
openapi.tuyaeu.comMost EU deployments
Region
Western Europe
openapi-weaz.tuyaeu.comProjects on the EU-West center
Region
India
openapi.tuyain.comDevices/accounts in India
Region
Singapore
openapi-sg.iotbing.comNewer SE-Asia allocation (added June 2025)
03
Real-time data
Stream events instead of polling.
Tuya's Message Queue pushes device status and alerts to your backend.
Common questions
Questions about the platform layer.
Does every custom Tuya app need Cloud API?
No. It earns its place when your team, business systems, or a new revenue line needs device data outside the app.
Should the platform layer be in the first release?
Only if launch depends on it. Otherwise, it is often a deliberate phase two.
How do I know if my product has a recurring or B2B path worth building for?
Products with a B2B buyer, multi-unit workflow, subscription, or premium tier often do. The scope review tests that case before you build.
Which Tuya data center and endpoint should we use?
Use the region where the app account and devices were registered. Unmapped countries default to Western America.
How does Tuya Cloud API authentication work?
A client ID and secret get an access token; each request is signed with HMAC-SHA256 and a timestamp. Cloud and app authorization use different signing modes.
How do we get real-time device status instead of polling?
Use Tuya's Pulsar-based Message Queue. It pushes status, online/offline events, and alerts without polling.
Start with the decision
Decide what belongs in your platform layer.
Separate must-have app work from platform work that can wait.