Documentation

Technical specification for the Spotify SMM Provider Engine, Smart Account Pool, and Gabo v2 Telemetry.

API & PlaygroundNew Order

System Architecture

The Spotify SMM System is a multi-platform provider engine built around real mobile and desktop client protocols, SQLite-persisted sticky device identities, and an automated Smart Account Pool.

Android Client (55%)

Client ID 9a8d2f0ce77a4e248bb71fefcb557637 · Spotify v9.1.28.2252 · Gabo Event-Service v2 Protobuf (RawCoreStream).

iOS Client (35%)

Client ID 58bd3c95768941ea9eb4350aaa033eb3 · iPhone16,2 / iOS 18.2 · Gabo Event-Service v2 Protobuf (RawCoreStream).

Web Player (10%)

Client ID d8a5ed958d274c2e8ee717e6a4b0971d · Chrome 131 · TrackPlayback & Connect State PUT.

Execution Lifecycle

  1. Order Ingestion: Orders arrive via POST /api/v2 (external SMM panels) or POST /api/orders (console UI).
  2. Smart Pool Acquisition: AccountPoolManager.acquire() selects the highest-scoring idle account that has not recently targeted the same URI and is under its 140/day stream cap.
  3. Warm Session Restoration: The worker restores the account's sticky hardware identity and reuses its cached access_token and client-token (valid for 28 minutes) without triggering redundant TOTP logins.
  4. Context Preparation & Audio CDN Streaming: Depending on the service's source_weights, the client executes a search, artist lookup, playlist fetch, or collection check, registers Connect State, downloads real byte ranges from audio-fa.scdn.co, and flushes Gabo v2 Protobuf events past the 30-second threshold.
  5. Pool Release & Cooldown: Metrics, updated token cache, and target URI history are persisted to SQLite, and the account enters a short post-task cooldown.