TSL Apps

Showing 25 of 34 from the live probe.

• Get Profile

  Your account: username, plan/tariff, trial status, and `balance` — the spendable wallet (own, or the team owner's). Check balance before paid actions.

• Get Stats

  The single stats endpoint — full-funnel metrics (clicks → installs → registrations → deposits → earnings) grouped by ONE dimension. This is exactly what the cabinet's Analytics section shows.

• List Pwas

  List your PWAs. Pass `period` to include per-PWA install/registration/deposit counts.

• Get Pwa

  Full PWA object — design (per language), tracker geo-offers, cloaking, per-device behaviour, push, analytics. Mind three name collisions when reading it: `category` on the PWA is its VERTICAL while `design.<lang>.category` is the free-text label visitors see; `name` is your internal label while `design.<lang>.app_name` is what visitors read; `creator_id` is the owning tenant (the TEAM id for team objects) while `buyer_id` is the individual.

• Create Pwa

  Create a draft PWA, optionally from a template (see list_templates). Returns pwa_id. Then configure with update_pwa, attach a domain, and go live with activate_pwa.

• Update Pwa

  Partial update — send only fields you change. Attach domains by setting `domains` (a domain may be shared by several PWAs, but attaching one that another PWA already holds is refused with 409 `domain_in_use` + the tenant list until you re-send with `allow_cotenancy: true`). `tracker` replaces the whole object, so send the full geo_offers list. Configure per-device behaviour via `additional`.

• Activate Pwa

  Launch (deploy) the PWA to every attached domain. Returns immediately with status `processing` — poll get_pwa until status is `active` (usually 1–3 min). Needs at least one domain. Also brings a `paused` PWA back online. EVERY language of the design must be filled in first (app_name, description, at least one screenshot, icon_url) — visitors get exactly their own language with no fallback, so an unfilled one is refused with `incomplete_languages`.

• Archive Pwa

  Archive (`archived: true`, an active PWA is also paused) or unarchive (`archived: false` → comes back paused; call activate_pwa to redeploy). Never deletes.

• Copy Pwa

  Clone a PWA (design, tracker, behaviour, push wiring) as a new draft with no domains. Attach domains + activate to launch the clone.

• List Templates

  Ready-made PWA store designs. Use a returned template_id with create_pwa.

• List Domains

  List domains connected to your account, with team-wide occupancy (which PWAs serve on each). Pass `period` for per-domain stats.

• Check Domain

  Check availability before connecting/buying. For type=system pass subdomain+base; for own/buy pass name.

• Add Domain

  Connect or acquire a domain. `own` — a domain you own (returns nameservers to set at your registrar). `system` — a free platform subdomain (subdomain + base; list bases via list_system_bases). `buy` — PURCHASE a domain through us (COSTS MONEY, charged to your balance).

• List System Bases

  Base domains you can hang a free subdomain on (for add_domain type=system): platform bases + your own active domains.

• Bulk Connect Domains

  Connect up to 50 of your own domains at once. Each result carries the nameservers to set at your registrar; domains sit `pending_ns` until delegation is detected.

• List Pixels

  List advertiser conversion pixels.

• Get Pixel

  Get one pixel with its event-matching config.

• Create Pixel

  Create a conversion pixel — SERVER-SIDE delivery of conversions to an ad network. Not the same as a PWA's `analytics` (browser tags) and not `tracker` (redirect routing). `events_matching` maps our events to the network's conversion names. Note the funnel wording here is `lead` and `sale` — the same two events that analytics and the visitor timeline call `registration` and `deposit`.

• Update Pixel

  Update a pixel — e.g. swap a banned pixel_code + access_token. Conversion delivery switches immediately, no PWA redeploy needed.

• Archive Pixel

  Archive (`archived: true`) or restore (`archived: false`) a pixel. Archived pixels stop firing conversions. Never deletes.

• Get Pwa Postbacks

  The server-to-server postback rules on a PWA — where we forward its conversions. At most one rule per event.

• Set Pwa Postbacks

  REPLACE-ALL the S2S postback rules on a PWA: send the complete set you want, and any event you omit is deleted (send an empty array to clear them all). One rule per event. URLs must be absolute http(s) and may carry macros like {click_id}, {payout}, {sub1}. Applies immediately — no redeploy needed. Read back delivery with list_outgoing_events(type='s2s'). Call get_pwa_postbacks first if you mean to ADD a rule rather than replace the set.

• List Push

  List push campaigns (and groups). Filter by category (`action` | `interval`), status, group_id, search.

• Get Push

  Get one push campaign (triggers/schedule/content/targeting).

• Create Push

  Create a push campaign. `action` campaigns fire on `triggers`; `interval` campaigns fire on a `schedule`. `content` = {title, body, icon, url}. See /openapi.json (PushCreate) for the full shape.