linkora.Open workspace

Build with Linkora

API documentation

Create an API key in your workspace. Add it as a Bearer token to requests under /api/v1. Read keys can fetch data; write keys can also create and change links. Every request is limited and scoped to the key owner.

MethodPathPurpose
POST/linksCreate a link (write key)
GET/linksList your links
GET/links/:idRead a link
PATCH/links/:idEdit a link (write key)
DELETE/links/:idDisable a link (write key)
GET/links/:id/statsViews, viewers, taps, daily totals
GET/links/:id/eventsPaginated activity
GET/links/:id/viewersPseudonymous viewer summary
GET/links/:id/viewer-statusCheck a Telegram ID
GET/links/:id/exportDownload a daily CSV

Create a link

POST /api/v1/links
Authorization: Bearer lk_your_key
Content-Type: application/json

{"url":"https://example.com/product?tag=affiliate-21","title":"Product link"}

The response contains the link ID, random code, Telegram short URL, status, and redirect delay. Custom codes may use 5–32 letters, numbers, underscores, or hyphens.

Analytics definitions

Views count recorded landing visits. Unique viewers count distinct verified Telegram users, with browser visitors counted by a limited anonymous ID. Outbound taps count Continue button presses. Automatic browser redirect attempts appear separately. Linkora cannot confirm the destination loaded.

Pagination and errors

List and activity endpoints take page (starting at 1). Link lists return up to 20 items per page and events up to 30. Private links you do not own return 404.

API keys

Create and revoke keys in the API Keys screen using your signed-in session. The complete key appears once. Store it outside source control. Revocation takes effect on the next request.