Skip to main content

Changelog

We guarantee backward compatibility for /v1. Every change is recorded here, including additions, changes and progress on known issues.

Adding a field is not a breaking change. Write your parser to ignore fields it does not recognize.

2026-09-18​

Documentation review​

  • Added genuine live-site screenshots in both languages, registration and sign-in steps, and code troubleshooting.
  • Corrected the September 17 claim that phone recovery was available: the signed-out entry remains unavailable and is separate from signed-in SMS password change.
  • Removed the blanket claim that every phone account can remain password-free; follow any password-setup prompt after verification.
  • Updated getting started, streaming, limitations, billing, renewal and FAQs to remove outdated browser-unavailable, direct-checkout and fixed-recovery-period claims.
  • Added conditions for expiry webhooks instead of promising delivery to every device.

This is a documentation revision, not a product feature release.

2026-09-17​

Account guidance​

  • Added phone/email sign-in guidance. A successfully verified phone number can create an account; follow subsequent initial-password prompts.
  • Phone login is the default, with an email tab and an SMS entry below the form when enabled.
  • Phone accounts may have no email and cannot use email recovery on that basis.
  • Changed expiry notification guidance to webhooks; conditions and limitations were clarified on September 18. See Renewal and Expiry.

2026-09-01​

Added​

  • Automation framework (8 /v1/automation/* endpoints): list workflow templates, dispatch in batches (up to 200 devices per request), view task status and step logs, and create, delete, enable or disable scheduled tasks. See the API documentation.
  • Template allowlist: official templates for automatic account registration, account nurturing/warm-up, random interactions and bulk private messaging cannot be dispatched. Requests return 403 with the category. Private templates are unaffected.
  • Automation quotas: counted by device executions, not requests; the default is 400 device executions per minute. Exceeding the quota returns 429. The response's unit field identifies the unit being counted.

Fixed​

  • The preview endpoint previously failed to return images. The adapter read a different field from the one returned upstream (accessUrl was returned, but the adapter read url), so ok was always false. This has been fixed, with a regression test requiring a URL whenever the result indicates success.

Known issue updates​

  • Live view in the browser: traced to missing web configuration for our appId in the upstream streaming scheduler. Cross-origin, network, account and device issues have been ruled out; the native PC connection works under the same conditions. Reported to the upstream provider.
  • Device provisioning time: measured at about 15 seconds for virtual devices and 18–30 minutes, with inconsistent timing, for cloud-hosted physical devices. The upstream provider does not expose a readiness signal that can be polled. Reported to the upstream provider.