Skip to main content

SDK and CLI coverage

This matrix describes checked-in clients, not a promise of full API parity. Collection responses expose next_page_token where the API supplies it; pass page_token on SDK lists that accept queries. New CLI container runs/lists and webhook deliveries accept --page-token and --limit.

Attachments and thread shape

Thread detail uses messages, matching the wire serializer; emails is not a thread field. Attachments are metadata on messages, threads and drafts. Upload bytes as inline base64 or a URL in a send/create-draft request; the API has no standalone attachment upload route. Download preserves the binary response:
Container stop is the exposed lifecycle control; container deletion and public port revocation have no SDK method because the current backend exposes neither. Provider configuration is required for paid resources; see Phone and Containers. Provider acceptance, queued mail and recipient delivery are distinct states. Inspect returned resource status before announcing success. Connections use hosted provider authorization, server-verified account status, retained old-account cleanup on reconnect, and revoke-before-delete on disconnect. See Connections and Billing for provider setup and recovery. Browser sessions use a native Cloudflare Browser Run BROWSER binding; an unconfigured workspace keeps creation disabled. Session state lasts until the session ends, with a 10-minute inactivity timeout and five-minute access links. Cross-session profiles and custom proxy routing are not exposed. See Browsers.