Use this flow to purchase a 30-day Cloud Phone term. Activation charges the team wallet. The caller must have Fees / Payment Management permission; otherwise activation returns 99012.
Local API requires MoreLogin desktop client v2.65.0 or later. Open API has no desktop-client dependency.
| Step | Open API | Local API |
|---|---|---|
| 1. Query plans | GET /cloudphone/monthly/skus | GET /api/cloudphone/monthly/skus |
| 2. Create inactive phones | POST /cloudphone/create | POST /api/cloudphone/create |
| 3. Charge and activate | POST /cloudphone/monthly/activate | POST /api/cloudphone/monthly/activate |
| 4. Query detail | POST /cloudphone/info | POST /api/cloudphone/info |
| 4. Query list | POST /cloudphone/page | POST /api/cloudphone/page |
- A request may contain different monthly SKUs. Validation and charging are all-or-nothing.
- If every phone belongs to the same paid order, activation restores that paid entitlement and does not charge again.
- A
33422response still includes the complete, request-ordereddata.results; inspect eachstatus,expireTime, anderrorCode. - After a timeout, query phone billing and expiry state before retrying. Do not assume a missing response means payment failed.
- Activation does not power on the phones and does not enable automatic renewal.
See Error Codes for the documented business and common errors.