Chat & broadcasts

TEASE gives you two messaging surfaces over one connected account: a unified DM inbox that surfaces the fans who are waiting on a reply first, and broadcasts — paced, ban-safe mass-messaging campaigns with audience preview and per-campaign ROI. Both are read and driven entirely through your al_live_* key.

How the pieces fit

Inbox

The inbox is a read surface. It lists conversations newest-waiting first, lets you open a single thread live, and returns a suggested price for any fan you are about to charge.

List conversations

GET /api/admin/inbox/conversations

Returns your threads ordered so that fans waiting on a reply rise to the top (longest wait first), then everything else by most-recent activity.

curl "https://app.tease.link/api/admin/inbox/conversations?status=open&limit=100" \
  -H "Authorization: Bearer $TEASE_API_KEY"

const res = await fetch(
  'https://app.tease.link/api/admin/inbox/conversations?status=open&limit=100',
  { headers: { Authorization: `Bearer ${process.env.TEASE_API_KEY}` } },
);
const { conversations, count } = await res.json();

import os, requests

res = requests.get(
    "https://app.tease.link/api/admin/inbox/conversations",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    params={"status": "open", "limit": 100},
)
data = res.json()

Query parameters

Response

{
  "conversations": [
    {
      "fan_id": "f_91kd2",
      "of_account_id": "acct_main",
      "platform": "of",
      "last_msg_ts": 1751290800,
      "last_inbound_ts": 1751290800,
      "last_outbound_ts": 1751280000,
      "unread_count": 2,
      "assigned_operator_id": null,
      "status": "open",
      "waiting_seconds": 10800
    }
  ],
  "count": 1
}

Read a thread

GET /api/admin/inbox/conversations/{fan_id}/messages

Opens one thread and returns its messages, read live from your connected account and normalized to a stable shape. Because bodies are not stored, this always reflects the true current state of the chat.

curl "https://app.tease.link/api/admin/inbox/conversations/f_91kd2/messages?limit=50" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Response

{
  "fan_id": "f_91kd2",
  "error": false,
  "messages": [
    {
      "msg_id": "m_88210",
      "ts": 1751290800,
      "direction": "in",
      "text": "hey is the new set out yet?",
      "price_cents": 0,
      "is_opened": true,
      "can_purchase": false,
      "media": []
    }
  ]
}

Price a fan

GET /api/admin/chatters/fan-pricing?fan_id={fan_id}

Returns a suggested PPV price and spend tier for one fan, derived from that fan's own purchase history on your account. The inbox calls this when you are about to send a priced message so the price fits the fan in front of you.

curl "https://app.tease.link/api/admin/chatters/fan-pricing?fan_id=f_91kd2" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Response

{
  "fan_id": "f_91kd2",
  "tier": "medium",
  "suggested_cents": 2000,
  "min_cents": 1400,
  "max_cents": 3200
}

The fans-waiting queue

GET /api/admin/chatters/waiting

A team-oriented cut of the same SLA: open threads with unread fan messages, longest wait first, with whales prioritized so a high-value fan does not sit in the queue.

curl "https://app.tease.link/api/admin/chatters/waiting?min_wait_min=5&limit=50" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Response

{
  "waiting": 1,
  "longest_wait_min": 180,
  "fans": [
    {
      "fan_id": "f_91kd2",
      "of_account_id": "acct_main",
      "unread_count": 2,
      "last_inbound_ts": 1751290800,
      "minutes_waiting": 180,
      "assigned_operator_id": null,
      "lifetime_net_cents": 6400,
      "tier": "medium"
    }
  ]
}

Send a DM (Beta)

POST /api/admin/inbox/send

Every call is screened, then routed through the gated engine. The response tells you exactly what happened with a single status verdict:

curl -X POST https://app.tease.link/api/admin/inbox/send \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "fan_id": "f_91kd2",
        "text": "new set just dropped — want it?",
        "media_ids": ["vault_55012"],
        "price_cents": 2000
      }'

Body parameters

Response

{
  "status": "shadow",
  "firewall": {
    "state": "ok",
    "reasons": [],
    "policy_version": "v3"
  },
  "outcome": {
    "mode": "shadow",
    "ok": true,
    "result": "shadow"
  }
}

Broadcasts

A broadcast is a campaign: pick an audience, write a message, preview the reach, then schedule it into a paced send plan. You build and inspect campaigns through the API; the delivery worker that drains the plan is gated (see below).

Delivery mechanism

Set mechanism when you create a campaign — this is how the message is delivered:

native is composed and previewed today; live delivery arrives with the sending engine (scheduling a native campaign returns an honest «появится после подключения движка» until then — it is never silently sent as 1to1).

Campaign modes

Set mode when you create a 1to1 campaign. The four modes shape how the audience is selected and how sends are sequenced (they don't apply to native, which is one blast).

Create a campaign

POST /api/admin/broadcasts

curl -X POST https://app.tease.link/api/admin/broadcasts \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "title": "June drop",
        "mode": "drip",
        "audience": { "tier": ["medium", "large", "whale"] },
        "message": {
          "steps": [
            { "text": "new set is live", "ppv_cents": 0 },
            { "text": "still time to grab it", "ppv_cents": 2500 }
          ]
        },
        "schedule": {}
      }'

const res = await fetch('https://app.tease.link/api/admin/broadcasts', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.TEASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    title: 'June drop',
    mode: 'drip',
    audience: { tier: ['medium', 'large', 'whale'] },
    message: {
      steps: [
        { text: 'new set is live', ppv_cents: 0 },
        { text: 'still time to grab it', ppv_cents: 2500 },
      ],
    },
    schedule: {},
  }),
});
const { id } = await res.json();

import os, requests

res = requests.post(
    "https://app.tease.link/api/admin/broadcasts",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    json={
        "title": "June drop",
        "mode": "drip",
        "audience": {"tier": ["medium", "large", "whale"]},
        "message": {"steps": [
            {"text": "new set is live", "ppv_cents": 0},
            {"text": "still time to grab it", "ppv_cents": 2500},
        ]},
        "schedule": {},
    },
)
campaign_id = res.json()["id"]

Body parameters

The response is the new campaign id:

{ "id": 42 }

List campaigns with GET /api/admin/broadcasts, and read one with GET /api/admin/broadcasts/{campaign_id} (see ROI & the drip funnel). Edit a draft with PATCH /api/admin/broadcasts/{campaign_id}.

Preview the audience

POST /api/admin/broadcasts/preview

Before you schedule, preview the reach. Preview resolves counts and a tier histogram only — it writes nothing and returns no PII: no fan ids, no names, just how many fans match.

curl -X POST https://app.tease.link/api/admin/broadcasts/preview \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "audience": { "tier": ["medium", "large", "whale"] } }'

Response

{
  "matched": 1840,
  "selected": 1720,
  "histogram": {
    "medium": 1100,
    "large": 480,
    "whale": 140
  }
}

Schedule a campaign (Beta)

POST /api/admin/broadcasts/{campaign_id}/schedule

Scheduling expands the campaign into a concrete, planned 1-on-1 send list and moves the campaign to scheduled. It returns how many recipients and planned sends were produced.

curl -X POST https://app.tease.link/api/admin/broadcasts/42/schedule \
  -H "Authorization: Bearer $TEASE_API_KEY"

Response

{
  "campaign_id": 42,
  "recipients": 1720,
  "planned_sends": 3440,
  "histogram": { "medium": 1100, "large": 480, "whale": 140 },
  "start_ts": 1751299200
}

A schedule call returns 409 if the campaign cannot be scheduled from its current status, or if a priced message is missing its media.

Pause, resume, cancel

Once scheduled, a campaign is controllable:

curl -X POST https://app.tease.link/api/admin/broadcasts/42/pause \
  -H "Authorization: Bearer $TEASE_API_KEY"

Each returns { "ok": true }, or 404 if the campaign does not exist in your account.

ROI & the drip funnel

GET /api/admin/broadcasts/{campaign_id}

Reading a campaign returns the full record plus two rollups: a send_status tally and a per-step by_step funnel — exactly what you need to see a drip drop off step by step.

{
  "id": 42,
  "title": "June drop",
  "mode": "drip",
  "status": "running",
  "recipients": 1720,
  "sent": 1610,
  "failed": 12,
  "skipped": 98,
  "purchases": 143,
  "revenue_cents": 357500,
  "send_status": {
    "sent": 1610,
    "pending": 0,
    "failed": 12,
    "skipped": 98
  },
  "by_step": [
    { "step": 0, "total": 1720, "sent": 1700, "failed": 8, "skipped": 12 },
    { "step": 1, "total": 1720, "sent": 1100, "failed": 4, "skipped": 616 }
  ]
}

What "ban-safe" means here

Every outbound path in this guide is built around one guarantee: you cannot accidentally get your account flagged through TEASE. Qualitatively, that means sends are screened for content before they move, delivered at a human-like pace with natural spacing, held back during quiet hours, and routed through a gate that is off by default. The exact pacing, timing, and screening rules are part of the safety layer and are deliberately not published — the contract you build against is the verdict (blocked / shadow / sent) and the campaign status, not the mechanism behind them.

Next steps

• Smart Links — trackable funnel links and per-link revenue.
• Attribution — revenue by source, country, and fan.
• Authentication — mint a scoped al_live_* key.
• API Reference — every inbox and broadcast endpoint.