# connect your landing page.

> The current leadli.me browser SDK contract: account-issued installation values, a marked Telegram CTA, and exact-origin verification.

The leadli.me browser SDK connects customer-owned landing pages to attribution. The account issues channel-specific values, observes the page, and verifies its exact origin. A separate read-only discovery API describes public product resources.

Updated October 2, 2026

## Get the installation code from leadli.me

Create a channel in the product and complete the Telegram and Meta steps. During landing setup, leadli.me provides the script URL, route key, temporary installation token, and fallback URL. Use the exact values from the product: the example below shows structure, not working credentials.

```html
<script
  src="https://sdk.leadli.me/v1.js"
  data-leadlime-route="ROUTE_FROM_LEADLI_ME"
  data-leadlime-installation="INSTALLATION_TOKEN"
  data-leadlime-fallback="https://t.me/your_channel"
  defer
></script>

<a href="https://t.me/your_channel" data-leadlime-subscribe>
  Open Telegram
</a>
```

## What installation verification checks

The script must load on the same origin confirmed in the product and find at least one element with data-leadlime-subscribe. A click creates an attribution record and requests an individual Telegram invite. If leadli.me is unavailable, the normal Telegram fallback must remain usable, but that join will be unattributed.

## Security and contract limits

A route key may appear in browser markup because it does not grant administrative access. The installation token is short-lived and used only for verification. Never place the Telegram bot token or Meta access token in HTML; those secrets are entered in the authenticated product and are not shown again after saving.

This page documents only the browser SDK. Internal endpoints used by the panel are not a supported public API for third-party integrations or agents.

## Reports through MCP

Subscriber and ad reports right in Codex, Claude Code, or another compatible MCP client. Your leadli.me data within your existing workflow.

## Read-only WebMCP tools

In browsers that support the experimental WebMCP API, the public site registers three read-only tools for product scope, pricing, and the guide index. They return the same Markdown resources available at direct URLs, do not use an authenticated session, and cannot create accounts, payments, or bookings.

## Public discovery API

The RFC 9727 API catalog, OpenAPI description, and health endpoint document public leadli.me resources for automated discovery. They do not expose accounts, attribution analytics, configuration, billing, or autonomous actions.

- API catalog: https://leadli.me/.well-known/api-catalog
- OpenAPI: https://leadli.me/openapi.json
- status: https://leadli.me/api/health

## Next step

[Open setup](https://app.leadli.me/register)

[Canonical HTML page](https://leadli.me/en/developers)