Skip to content
Last updated

Monthly Cloud Phone Purchase

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.

Purchase flow

Cloud Phone providerWallet and order serviceMoreLogin APIYour applicationCloud Phone providerWallet and order serviceMoreLogin APIYour application1. Query monthly SKUsskuId and 30-day price2. Create Cloud PhoneProvision instanceInactive Cloud Phone IDs (no charge)3. Activate monthly phonesValidate order and charge or restorePaid entitlementActivate 30-day termorderId and ordered results4. Query phone stateBilling, expiry, and readiness state
Cloud Phone providerWallet and order serviceMoreLogin APIYour applicationCloud Phone providerWallet and order serviceMoreLogin APIYour application1. Query monthly SKUsskuId and 30-day price2. Create Cloud PhoneProvision instanceInactive Cloud Phone IDs (no charge)3. Activate monthly phonesValidate order and charge or restorePaid entitlementActivate 30-day termorderId and ordered results4. Query phone stateBilling, expiry, and readiness state

API paths

Billing and recovery rules

  • 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 33422 response still includes the complete, request-ordered data.results; inspect each status, expireTime, and errorCode.
  • 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.