LnkAppDevelopers
Developer docs: the link API
From an API key to a resolving link in one call. The full v1 surface is documented, and webhooks close the loop into your own systems.
A link in one API call
One authenticated call creates a link. From there, the rule is parity: everything you can do in the dashboard, you can do in the API. Build against the documented v1 surface and the dashboard never becomes a manual step in your pipeline. Read the docs.
- Everything in the dashboard is in the API Verifiable · per-release
In depth
The API is the product, not a companion feature. The parity rule is deliberate and testable: if the dashboard can do it, the API can do it — links, custom domains, analytics reads, and webhook configuration included.
What that means in practice:
- Automation is first-class. Anything your team clicks today can become a call in your deployment or campaign pipeline tomorrow.
- The docs are the contract. The public API documentation covers the v1 surface and moves with each release — start at the quickstart, which takes you from a key to a resolving link in one call.
- Events flow back. Pair the API with webhooks to close the loop into your own systems.
Read the docs.
Webhooks that close the loop
Events push into your systems with the failure handling already engineered: retries when your endpoint has a bad moment, circuit breakers when it has a bad hour, dead-letter queues so nothing vanishes silently. You build the consumer; delivery discipline is our job.
- Webhooks with delivery guarantees: retries, circuit breakers, dead-letter queues Verifiable · per-release
In depth
A webhook system is judged by what happens when the receiving end misbehaves. This one is engineered for exactly that day:
- Retries. Transient failures on your side are retried — a blip does not cost you the event.
- Circuit breakers. A persistently failing endpoint is isolated instead of hammered, and delivery resumes sanely when it recovers.
- Dead-letter queues. Events that exhaust their delivery attempts land somewhere inspectable — failure is visible and recoverable, never silent.
The delivery behavior is part of the documented API surface, so what your integration can rely on is written down, not folklore.