API and widget

Embed LiKE AI search into your applications, website, or internal systems. Three integration methods: REST API, JS widget, iframe.

#REST API

#Step 1 — Create an API key

1. Integrations → Public API → "Create key"
2. Enter a name (for example, "Mobile app")
3. Copy the key — it is shown only once

#Step 2 — Use the API

All requests are authorized via the header:

X-API-Key: your-key

#Core endpoints

#Example: AI search

curl -X POST https://amedia.lynkora.pro/api/public/search \
  -H "X-API-Key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "Как оформить отпуск?"}'

Response:

{
  "answer": "Для оформления отпуска...",
  "sources": [
    {"title": "Политика отпусков", "url": "..."}
  ]
}

#Rate limits

API requests are throttled per key. The specific limit depends on your plan; when it is exceeded, HTTP 429 is returned with a Retry-After header. The exact values for your plan are in the plan section.

#Security

1. Store keys in environment variables, not in code
2. Create a separate key for each application
3. Delete unused keys
4. Restrict domains in the key settings

#JS widget

A floating AI search button to embed on any website.

#Step 1 — Get the code

1. Integrations → JS Widget
2. Configure the parameters (see the table below)
3. Copy the code

#Step 2 — Add it to your site

Insert the copied <script> before the closing </body> tag:

#Widget parameters

#Result

A purple button appears in the corner of your site. Click → a modal window with a search bar → an AI answer from your knowledge base.

#iframe

A full-featured search interface embedded on your page:

#Embed code

#Direct link

If an iframe does not suit you, give users a direct link: https://amedia.lynkora.pro

#Demo mode

For testing without an API key, a demo endpoint is available with limitations:

Endpoint: POST /api/public/demo/search

#Comparison of authentication modes

The widget supports two authentication modes.

#Mode A — Trust the URL zone

Client-side authentication: you are responsible for who reaches the pages with the widget (VPN, SSO, protected routes). Lynkora does not know the user's identity — only the request's Origin/IP. The widget is visible to everyone who opens a page with the embed code.

• Backend code: 0 lines
• Onboarding time: ~2 minutes
• Suitable for: intranet, internal portal

#Mode B — Session token (per-user JWT)

Your backend issues a short-lived session token for each user. Lynkora knows the identity, keeps an audit per user, and supports revocation and GDPR DSAR.

• Backend code: ~10 lines (via SDK)
• Onboarding time: 1–2 hours
• Suitable for: multi-tenant SaaS, regulated industries