Landing pages

A landing page is the public funnel TEASE serves on one of your domains. You compose it from ordered geo-segments, a stack of buttons per segment, an optional notification banner, and a background — all edited as a draft, previewed live, then published in one atomic step.

Every change you make through the API writes to the draft state only. The live page never moves until you call /publish. That gives you a safe edit-preview-ship loop with a single global undo (/discard).

Concepts

Domains

A domain row is the anchor for an entire landing page. List the domains you own, create new ones, and copy a finished page onto another domain.

List domains

curl https://app.tease.link/api/admin/domains \
  -H "Authorization: Bearer $TEASE_API_KEY"

const res = await fetch('https://app.tease.link/api/admin/domains', {
  headers: { Authorization: `Bearer ${process.env.TEASE_API_KEY}` },
});
const { items } = await res.json();

import os, requests

res = requests.get(
    "https://app.tease.link/api/admin/domains",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
)
items = res.json()["items"]

{
  "items": [
    {
      "hostname": "links.creator.com",
      "display_name": "Instagram bio",
      "created_at": 1751280000,
      "button_count": 4,
      "infra_state": "ssl_active",
      "provisioning_error": null,
      "infra_attempted_at": 1751280000
    }
  ]
}

Each row carries an infra_state that drives the status badge in the dashboard:

Create a domain

curl -X POST https://app.tease.link/api/admin/domains \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "hostname": "links.creator.com", "display_name": "Instagram bio" }'

const res = await fetch('https://app.tease.link/api/admin/domains', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.TEASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ hostname: 'links.creator.com', display_name: 'Instagram bio' }),
});
const domain = await res.json();

res = requests.post(
    "https://app.tease.link/api/admin/domains",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    json={"hostname": "links.creator.com", "display_name": "Instagram bio"},
)
domain = res.json()

Parameters

A new domain is created with infra_state: "provisioning" and seeded with three default geo-segments plus empty notification/background rows, so it is editable immediately. Re-creating a hostname you already own within a minute returns the existing row (idempotent retry); otherwise a duplicate returns 409 domain_taken.

Rename or delete a domain

PATCH updates the display_name (it is reporting metadata only and takes effect without a publish). DELETE removes the domain and cascades its buttons, segments, banner, and background.

# Rename
curl -X PATCH https://app.tease.link/api/admin/domains/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "display_name": "TikTok bio" }'

# Delete
curl -X DELETE https://app.tease.link/api/admin/domains/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY"

await fetch('https://app.tease.link/api/admin/domains/links.creator.com', {
  method: 'PATCH',
  headers: {
    Authorization: `Bearer ${process.env.TEASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ display_name: 'TikTok bio' }),
});

requests.patch(
    "https://app.tease.link/api/admin/domains/links.creator.com",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    json={"display_name": "TikTok bio"},
)

Copy a page onto another domain

copy-from replaces the target's draft buttons and segments with copies of a source domain's — a full draft clone you then publish. The page is rebuilt with fresh button identities so the live page refreshes cleanly.

curl -X POST https://app.tease.link/api/admin/domains/new-site.com/copy-from \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "source": "links.creator.com" }'

Custom domains

To serve a page on your own domain, connect it and verify DNS. Connect is a small state machine built on infra_state: a connect request opens the domain in pending_dns, and a successful verify flips it to active.

curl -X POST https://app.tease.link/api/admin/domains/connect \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "hostname": "links.creator.com" }'

{
  "domain_id": 42,
  "hostname": "links.creator.com",
  "is_apex": false,
  "state": "pending_dns",
  "instructions": { "record_type": "CNAME", "name": "links", "value": "…" },
  "verify_url": "/api/admin/domains/42/verify"
}

{
  "domain_id": 42,
  "hostname": "links.creator.com",
  "state": "pending_dns",
  "issues": ["CNAME not found"]
}

{
  "domain_id": 42,
  "hostname": "links.creator.com",
  "state": "active",
  "url": "https://links.creator.com"
}

The state machine is intentionally small — there are only two outcomes from pending_dns:

Segments

A geo-segment is an audience bucket. Visitors are matched to the first segment whose conditions fit, falling through to the one default catch-all. Each segment owns its own ordered button stack, so you can show a different funnel to (say) US mobile traffic than to everyone else.

A segment matches primarily by country. You can optionally narrow it with display conditions on device, OS, or time of day, and tag it with a target language for auto-translation.

Segments have their own «Сегменты» tab in the domain hub (/domains/<domain>/segments), next to «Кнопки». It lists every segment as a card in priority order (top matches first) — its countries and conditions, the default / block flags, the button-set A/B split, and up/down priority arrows. The segment's actual buttons are still edited in the «Кнопки» tab.

Country tiers

Your account has three reusable country tiers, shared across every domain:

• Tier 1 — your top-paying markets.
• Tier 2 — your mid markets.
• Blocklist — countries you turn away with a 403 (they never enter the funnel).

They power two things: the T1 / T2 preset chips in the segment editor add the countries from your Tier 1 / Tier 2 to the segment you're building, and traffic is automatically A/B-weighted by tier (Tier 1 leans more aggressively toward the paid offer than Tier 2).

The tiers stay behind the scenes — they seed the preset chips and the A/B split, not a settings screen of their own. Every account starts with sensible defaults; to customise them, use the API/MCP get_config / set_config (the geo_classify key — { "tier1": [...], "tier2": [...], "blocklist": [...] } of ISO-3166 alpha-2 codes). Your changes apply only to your account.

List segments

curl https://app.tease.link/api/admin/segments/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "domain": "links.creator.com",
  "items": [
    {
      "segment_id": "s_1a2b3c4d",
      "domain": "links.creator.com",
      "name": "US mobile",
      "countries": ["US"],
      "position": 0,
      "is_default": false,
      "match": [{ "type": "device", "op": "is", "values": ["mobile"] }],
      "ab": null,
      "lang": ""
    },
    {
      "segment_id": "s_default",
      "domain": "links.creator.com",
      "name": "Everyone",
      "countries": [],
      "position": 1,
      "is_default": true,
      "match": null,
      "ab": null,
      "lang": ""
    }
  ]
}

Create a segment

curl -X POST https://app.tease.link/api/admin/segments/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "US mobile",
    "countries": ["US"],
    "match": { "all": [{ "type": "device", "op": "is", "values": ["mobile"] }] }
  }'

Parameters

Match clauses

A match clause narrows a segment beyond country. Each clause is one of:

Within a clause, values are OR-ed; across clauses in all, conditions are AND-ed.

Edit, reorder, delete

PATCH accepts any subset of the create fields. Omitting a field leaves it unchanged; sending an explicit empty conditions payload clears it.

# Edit
curl -X PATCH https://app.tease.link/api/admin/segments/links.creator.com/s_1a2b3c4d \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "countries": ["US", "CA"] }'

# Reorder — the list must be a permutation of the domain's current segment ids
curl -X PUT https://app.tease.link/api/admin/segments/links.creator.com/order \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "order": ["s_1a2b3c4d", "s_default"] }'

# Delete — pass ?force=true to also remove the segment's buttons
curl -X DELETE "https://app.tease.link/api/admin/segments/links.creator.com/s_1a2b3c4d" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Order matters: segments are considered top-to-bottom, so place your most specific segments above the catch-all. Reorder validates that your order array is exactly the current set of segment ids (order_mismatch otherwise). Deleting a segment that still has buttons returns 409 segment_has_buttons unless you pass ?force=true; deleting the default returns 400 segment_default_required until you promote another segment first.

Direct redirects

Sometimes the landing itself is the wrong layer for an audience — you want the visitor on the destination instantly. Two levels of direct 307 redirects cover that, and both keep every hop logged and attributed like any other click.

Redirect segments

A segment can be flagged as a redirect segment: a visitor it matches never sees the landing — they are 307-redirected straight to that segment's primary button destination (the bottom-most one, the same button the landing paints as its main CTA). The hop is recorded as a click with its own source label, so redirected countries stay visible in your traffic reports and feed Telegram attribution. A block segment always wins over a redirect — a blocked country still gets its 403. The flag itself is provisioned by the platform for messenger-bound geo routes; it is not yet self-serve in the segment editor.

Direct-redirect mode (per domain)

A whole domain can skip its landing: with direct-redirect mode on, TEASE geo-matches the visitor to a segment as usual and then 307s them straight to that segment's button destination — for a smart-link button that is the domain's /r/<slug> smart link, so click logging, click-id binding, and revenue attribution keep working end-to-end. Built for placements where an interstitial page only loses clicks (e.g. adult X/Twitter traffic).

curl -X POST https://app.tease.link/api/admin/domains/links.creator.com/direct-redirect \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": true, "ab_pct": 0 }'

{ "domain": "links.creator.com", "direct_redirect": true, "ab_pct": 0 }

The guardrails you'd expect all stay on:

• The redirect target comes from the published page, so the toggle needs no re-publish and takes effect within about a minute. In the panel it is the «Прямой редирект» button next to «Импорт», above the button list.
• The target is the audience's primary button — the bottom-most one, the same button the landing paints as its main CTA. The setting is per DOMAIN: it applies in EVERY audience, and each one sends its visitors to its own primary button.
• Redirect and block segments still win: a matched redirect segment sends its own 307 (e.g. to Telegram), and a blocklisted country still gets 403.
• Bots and scanners never see the destination — they get nothing, exactly like the cloaking layer.
• In-app webviews (Instagram / Facebook / TikTok embedded browsers) still receive the landing: the destination won't open inside a hardened webview, so the landing's client-side escape must run there.
• If the matched segment has nothing to redirect to, the landing is served — a fail-safe, never a dead redirect.

A/B: landing vs. straight-to-offer

ab_pct turns the on/off into a live experiment on an enabled host: N% of visitors get the direct redirect (arm B), the rest get the normal landing funnel (arm A). 0 means everyone is redirected (no A/B); 100 states the same thing explicitly. The split is sticky per visitor and cookieless, and entry clicks carry the arm tag, so conversions attribute per arm — you measure which converts better instead of committing 100%. Domain rows in GET /api/admin/domains report direct_redirect and direct_redirect_ab_pct.

Buttons

Buttons live inside a segment. When managing buttons, the segment's segment_id is the tier path parameter — so buttons/{domain}/{segment_id} is "the buttons shown to this audience".

List a segment's buttons

curl https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "domain": "links.creator.com",
  "tier": "s_1a2b3c4d",
  "items": [
    {
      "button_id": "main",
      "domain": "links.creator.com",
      "tier": "s_1a2b3c4d",
      "position": 0,
      "label": "Subscribe",
      "text_value": "Subscribe",
      "url": "https://example.com/offer",
      "icon": "heart.svg",
      "hidden": false,
      "match": null,
      "variants": null,
      "popup": null
    }
  ]
}

Create a button

curl -X POST https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text_value": "Subscribe",
    "url": "https://example.com/offer",
    "icon": "heart.svg"
  }'

Parameters

Editing and ordering mirror segments:

# Edit any subset of fields
curl -X PATCH https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d/main \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "text_value": "Join now" }'

# Reorder within the segment
curl -X PUT https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d/order \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "order": ["main", "secondary"] }'

# Delete
curl -X DELETE https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d/main \
  -H "Authorization: Bearer $TEASE_API_KEY"

Teaser popup

Any button can carry a teaser popup — a small card with a photo and up to 160 characters of text that slides out under the button after a delay. Tapping the card clicks the button itself. A popup shows at most once per pageview, and a visitor who dismisses it won't see it again for the rest of their session.

Configure it in two steps: upload the photo (auto-cropped to a 480×360 WebP card), then set the popup object on the button via create or PATCH.

# 1. Upload the card photo (multipart, max 5 MB)
curl -X POST https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d/main/popup-photo \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -F "file=@teaser.jpg"

{ "filename": "popup_9f2c1a7b3d4e.webp", "url": "/notification/links.creator.com/popup_9f2c1a7b3d4e.webp" }

# 2. Attach the popup to the button
curl -X PATCH https://app.tease.link/api/admin/buttons/links.creator.com/s_1a2b3c4d/main \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "popup": {
      "enabled": true,
      "text": "Tonight’s set is 50% off — 2 hours only",
      "delay_ms": 4000,
      "photo": "popup_9f2c1a7b3d4e.webp"
    }
  }'

Popup fields

The popup object replaces the stored popup wholesale. Re-uploading identical photo bytes is idempotent (same content → same filename), so retries are safe.

Icons

Every button references an icon by filename. The icon library ships ~290 built-in icons — brand marks plus generic glyphs, searchable and categorised in the panel's icon picker — and holds your own uploads next to them. Built-ins are shared; anything you upload or generate is private to your workspace.

# List everything you can use (built-ins + your own)
curl https://app.tease.link/api/admin/icons \
  -H "Authorization: Bearer $TEASE_API_KEY"

# Upload your own SVG (sanitized, max 1 MB)
curl -X POST https://app.tease.link/api/admin/icons \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -F "file=@custom.svg"

Generate an icon with AI

Can't find the right glyph? POST /api/admin/icons/generate draws a new icon in the house style — white on a transparent background, so it sits next to the built-ins seamlessly — and saves it straight to your private library.

curl -X POST https://app.tease.link/api/admin/icons/generate \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "prompt": "paper plane", "style": "line" }'

{ "filename": "gen_7c2f91d3a4b5.svg", "builtin": false, "uploaded_at": 1752537600 }

Use the returned filename as a button's icon. Generation is rate-limited to 6 per minute (429 icon_gen_rate_limited); a failed attempt returns 502 icon_ai_failed — just retry with a reworded prompt.

Notification banner

The banner is a per-domain, push-style card (avatar, title, body, and a call-to-action link) that appears on the page after a short delay. There is one banner per domain — you can edit it by hand, or drive it from the reusable notification library (where two or more enabled presets turn it into a creative A/B test).

Read and edit

curl https://app.tease.link/api/admin/notification/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "domain": "links.creator.com",
  "enabled": true,
  "avatar_filename": "av_9f.png",
  "sound_filename": null,
  "title": "New drop",
  "body": "Tap to see today's set",
  "link_text": "Open",
  "target_url": "https://example.com/offer",
  "delay_ms": 2500,
  "translations": {},
  "style": null,
  "preset_id": null,
  "assignment": null
}

PATCH accepts any subset of the editable fields:

curl -X PATCH https://app.tease.link/api/admin/notification/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true,
    "title": "New drop",
    "body": "Tap to see today’s set",
    "link_text": "Open",
    "target_url": "https://example.com/offer",
    "delay_ms": 2500
  }'

Parameters

Where the click goes

The banner's call-to-action has two modes, switched by link_mode:

• Smart link ("", the default) — a click mirrors the primary button of the segment the visitor matched, following the exact tier-aware routing (and A/B arm) the buttons themselves use. No URL is needed to enable the banner in this mode; a stored target_url serves only as a last-resort fallback when the matched segment has no button to mirror.
• Own link ("manual") — the banner goes exactly where you point it: target_url is required (enabling without it returns 400 notification_incomplete) and wins over the segment mirror.

Appearance

The banner's look is styled independently of its content: the style object on the same PATCH carries the appearance knobs. Only the keys you set are stored; send {} to reset the banner to the stock look. The current value comes back in the style field on reads.

curl -X PATCH https://app.tease.link/api/admin/notification/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "style": {
      "theme": "glass",
      "opacity": 0.9,
      "radius": 18,
      "avatar_shape": "circle",
      "position": "top",
      "accent": "#e0426e"
    }
  }'

Avatar and sound

The avatar image and optional notification sound are uploaded as files and can be removed:

# Upload an avatar (multipart)
curl -X POST https://app.tease.link/api/admin/notification/links.creator.com/avatar \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -F "file=@avatar.png"

# Remove the sound
curl -X DELETE https://app.tease.link/api/admin/notification/links.creator.com/sound \
  -H "Authorization: Bearer $TEASE_API_KEY"

Notification library & A/B

Instead of hand-editing every domain, keep your banner creatives as reusable presets in the notification library and assign them to domains. In the panel, the «Уведомление» tab is a wall of preset cards with checkboxes: a checked card is what the domain shows, two or more checked cards run a creative A/B test, and each card's weight sets its share of impressions. A given visitor sticks to one variant (rotation is sticky per subnet), so the test stays clean.

A preset carries the full creative — texts, the call-to-action link, delay, translations, plus its own master files (avatar/sound), stored under notification/_preset_<id>/ and served at /notification/_preset_<id>/<filename>. Whenever a preset is put on a domain, those masters are copied into the domain's folder, so the live banner never references a file that isn't there.

# List the library
curl https://app.tease.link/api/admin/library/notifications \
  -H "Authorization: Bearer $TEASE_API_KEY"

# Save a domain's current banner into the library — files included
curl -X POST https://app.tease.link/api/admin/library/notifications/from-domain \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "domain": "links.creator.com", "name": "July drop" }'

from-domain snapshots the domain's draft banner into a new preset together with its avatar/sound files and stamps the new preset_id back onto the domain, so the card shows its library binding. Errors: 400 name_required / 400 notification_empty (nothing to save), 409 preset_name_taken, 404 domain_not_found.

Assign presets to a domain

The assignment object on the banner PATCH is the API behind the checkboxes. It replaces the stored assignment wholesale; { "items": [] } clears it (back to the hand-edited single banner).

curl -X PATCH https://app.tease.link/api/admin/notification/links.creator.com \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "assignment": {
      "items": [
        { "preset_id": 7, "weight": 2, "enabled": true },
        { "preset_id": 9, "weight": 1, "enabled": true },
        { "preset_id": 4, "enabled": false }
      ]
    }
  }'

Every enabled preset is validated on save: an unknown id returns 404 preset_not_found, and a preset that is missing its texts, avatar, or — in the own-link mode — its link returns 400 preset_incomplete — a broken arm can never silently eat a share of your traffic. The first enabled preset is stamped into the domain banner (texts, files, and preset_id) and every enabled preset's master files are copied into the domain folder, so a single-preset assignment serves its creative immediately.

Preset avatars

Each preset owns a master avatar, managed on the preset itself (multipart image up to 5 MB, center-cropped to a 192 px square WebP with a content-hash filename):

# Upload / replace the master avatar
curl -X POST https://app.tease.link/api/admin/library/notifications/7/avatar \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -F "file=@avatar.jpg"

# Remove it (bound domains lose it too and their banners are disabled)
curl -X DELETE https://app.tease.link/api/admin/library/notifications/7/avatar \
  -H "Authorization: Bearer $TEASE_API_KEY"

In the panel you can pick the avatar straight from your photo gallery or upload a new image — an uploaded photo is saved into the gallery as well, so it's reusable next time.

Editing and applying presets

PATCH /api/admin/library/notifications/{preset_id} edits propagate immediately: every domain whose assignment enables the preset is re-stamped and its draft re-baked, so a text or avatar fix reaches all bound drafts in one call — going live stays an explicit /publish. POST /api/admin/library/notifications/{preset_id}/apply (body { "domains": [...] }) stamps a preset onto whole domains at once: it writes a single-preset assignment, materializes the master files into each domain folder, and enables the banner only when the preset is complete (all texts, an avatar, and — in the own-link mode — the link).

Enabling follows preset readiness. On every re-stamp the bound domains' enabled is derived from the preset itself: the assignment checkbox records the intent to show, and the banner turns on automatically the moment the preset becomes complete (all texts, an avatar, and — in the own-link mode — the link) — say, when the missing avatar finally lands in the card — and honestly turns off when the preset stops being complete.

Background

Each domain has a background made of up to three pieces: a mobile image, a desktop image, and a solid canvas colour painted behind the card on desktop. Images go through an upload step and an edit step; the canvas colour is a single call.

Quick pick: in the «ник модели» card (the «Кнопки» tab), clicking the avatar opens the background library — choose one (→ single bg) or several (→ random rotation) without leaving the buttons editor. Uploading and cropping new backgrounds still lives in the «Дизайн» tab.

Upload and edit an image

bg/upload saves the original image for a (domain, variant) pair, where variant is mobile or desktop. bg/edit applies your crop/transform design state and regenerates the served variants.

# 1. Upload the source image for the mobile background
curl -X POST "https://app.tease.link/api/admin/bg/upload?domain=links.creator.com&variant=mobile" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -F "file=@bg-mobile.jpg"

# 2. Commit the editor design state
curl -X POST "https://app.tease.link/api/admin/bg/edit?domain=links.creator.com&variant=mobile" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "designState": { } }'

const form = new FormData();
form.append('file', file); // a Blob/File of the image
await fetch(
  'https://app.tease.link/api/admin/bg/upload?domain=links.creator.com&variant=mobile',
  { method: 'POST', headers: { Authorization: `Bearer ${process.env.TEASE_API_KEY}` }, body: form },
);

Canvas colour

curl -X POST "https://app.tease.link/api/admin/bg/canvas-color?domain=links.creator.com" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "color": "#0d0604" }'

Button appearance

Built-in (platform) designs expose a landing-wide button style — shape, fill, opacity, colours, label contrast, typography, icon colours, alignment, and an idle animation. It follows the same draft → publish lifecycle as everything else and is set through POST /api/admin/bg/ui, which carries three independent sections: buttons (this one), profile, and gate. In the panel they live in the domain hub («Дизайн» / «Лендинг»), with a live preview of every knob.

A section object replaces the stored section wholesale (send the full style you want); null resets it to the stock look. Only the keys you set are stored — anything omitted keeps the design's default.

curl -X POST "https://app.tease.link/api/admin/bg/ui?domain=links.creator.com" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "buttons": {
      "shape": "pill",
      "fill": "solid",
      "opacity": 0.95,
      "color": "#e0426e",
      "text": "auto",
      "animation": "breathe",
      "anim_speed": "slow",
      "font": "unbounded",
      "align": "icon_left"
    }
  }'

# Back to the stock look
curl -X POST "https://app.tease.link/api/admin/bg/ui?domain=links.creator.com" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "buttons": null }'

See Style every button on the landing page for a full worked example, and Landing-page builder for the free-canvas layout, teaser stack, sticky bar, spotlight and appear-rules surface that lives alongside this section.

Fonts

The same twelve-face brand pack powers every typography knob on the page — button labels (buttons.font), the profile card (name_font / bio_font), and the notification banner (style.font):

Latin-only faces (satoshi, clashdisplay, bebas) have no Cyrillic glyphs — Cyrillic text set in them falls back to the brand default face automatically, so a Russian label never renders as tofu. Font ids from the retired v1 pack keep working on read: they simply render as the default.

Changing font re-renders every button label of the domain in the new face on the server (labels are pre-baked SVGs) — the response reports the count as relabeled. All faces are self-hosted under free licenses and served same-origin from your domain (/fonts/lf_<id>.woff2), so the page never makes a third-party font request.

Profile card

The same bg/ui endpoint styles the profile card above the buttons — the nickname's typeface and size, the "Active now • Responds in 5 mins" status line, and an optional bio with its own typeface and size — via the second section, profile. Platform designs only, same draft → publish lifecycle, same replace-wholesale semantics: send the full section you want, or { "profile": null } to reset to the stock card.

curl -X POST "https://app.tease.link/api/admin/bg/ui?domain=links.creator.com" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "profile": {
      "name_font": "unbounded",
      "name_size": 1.2,
      "status_text": "Online now",
      "bio": "18+ • daily drops",
      "bio_font": "nunito",
      "bio_size": 0.9
    }
  }'

18+ content gate

The same bg/ui endpoint carries an optional 18+ sensitive-content gate — a confirmation step shown before the page: either a full-screen cover (optionally blurring the page behind it) or a compact sheet from the top edge. A visitor confirms once per browser and is never asked again. Platform designs only, same draft → publish lifecycle.

curl -X POST "https://app.tease.link/api/admin/bg/ui?domain=links.creator.com" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "gate": {
      "enabled": true,
      "mode": "cover",
      "blur": true,
      "title": "Adults only",
      "text": "This page contains sensitive content.",
      "ok": "I’m 18 or older",
      "leave": "Leave",
      "leave_url": "https://google.com"
    }
  }'

Send { "gate": null } to remove the gate entirely.

Desktop-wide mode, free canvas, stack, sticky bar & appear rules

bg/ui carries several more sections beyond buttons/profile/gate — full walkthroughs live under Landing-page builder, summarised here so the whole bg/ui surface is in one place:

Languages & auto-translate

Segments carry an optional lang target, and the notification banner carries a translations map, so the public text can be auto-translated per locale. The translations object is keyed by language code and only ever holds the public text fields:

{
  "translations": {
    "es": { "title": "Nuevo drop", "body": "Toca para ver el set de hoy", "link_text": "Abrir" },
    "fr": { "title": "Nouveau drop", "link_text": "Ouvrir" }
  }
}

Supported codes include en, ru, pt, es, de, fr, it, nl, pl, tr, ar, hi, id, ja, ko, zh. The call-to-action destination is never part of a translation — only the visible title, body, and link_text.

QR codes

Every domain can hand out printable QR codes — a flyer, a sticker, a business card — that lead straight to the landing page and are tracked like any other traffic source, live outside the draft/publish cycle. See QR codes for creating, designing, downloading, reading a code's funnel, and renaming or disabling one without devaluing what's already printed.

Draft → preview → publish

Everything above writes to the draft. Nothing is live until you publish. The recommended loop:

curl https://app.tease.link/api/admin/config \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "is_dirty": true,
  "dirty_domains": ["links.creator.com"],
  "draft": { "updated_at": 1751280600, "domains": {}, "segments": {}, "notifications": {}, "backgrounds": {} },
  "published": { "updated_at": 1751280000, "domains": {}, "segments": {}, "notifications": {}, "backgrounds": {} }
}

curl "https://app.tease.link/api/admin/preview-token?domain=links.creator.com&force_country=US&force_device=mobile" \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "token": "…",
  "public_url": "https://links.creator.com",
  "frame_path": "/preview-frame/"
}

Publish and discard

POST /api/admin/publish copies the draft to the live page atomically. With no body it publishes every dirty domain; pass a domains array to publish only some.

# Publish everything that changed
curl -X POST https://app.tease.link/api/admin/publish \
  -H "Authorization: Bearer $TEASE_API_KEY"

# Publish only one domain
curl -X POST https://app.tease.link/api/admin/publish \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "domains": ["links.creator.com"] }'

await fetch('https://app.tease.link/api/admin/publish', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.TEASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ domains: ['links.creator.com'] }),
});

requests.post(
    "https://app.tease.link/api/admin/publish",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    json={"domains": ["links.creator.com"]},
)

{ "ok": true, "bg_files_by_domain": {}, "domains": ["links.creator.com"] }

Publishing with nothing changed returns 400 nothing_to_publish. POST /api/admin/discard takes the same optional domains selection and restores the draft from published; with nothing to undo it returns { "ok": true, "noop": true }.

Audit feed

Every change above is journaled. GET /api/admin/audit returns the most recent entries (newest first), useful for an activity feed or change log.

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

{
  "items": [
    {
      "id": 9012,
      "ts": 1751280600,
      "actor": "owner",
      "action": "publish",
      "payload": "{\"tiers_updated\": true}"
    }
  ]
}

FAQ

Next steps