Developer reference

SLAtech v1 API — public endpoints

9 public endpoints — bot query (sync + streaming), lead capture, landing-page payloads, pricing JSON, public stats, widget analytics. Curl examples are copy-paste runnable; auth notes и rate-limit headers are documented in the FAQ at the bottom.

Endpoints

9 routes, plain JSON over HTTPS

POST /v1/query/ask

Submit a visitor question and receive a RAG-grounded answer + citation sources.

curl -X POST https://api.slatech.ai/v1/query/ask \
  -H 'Content-Type: application/json' \
  -H 'X-Site-Id: {SiteId GUID}' \
  -d '{
        "question": "Do you accept walk-in appointments?",
        "topK": 10,
        "scoreThreshold": 0.5
      }'
POST /v1/query/ask-stream

Same as /ask but streams the answer token-by-token via Server-Sent Events.

curl -N -X POST https://api.slatech.ai/v1/query/ask-stream \
  -H 'Content-Type: application/json' \
  -H 'X-Site-Id: {SiteId GUID}' \
  -d '{ "question": "How do you handle no-shows?" }'
# SSE events: { event: "token", data: "..." }, { event: "done", data: { sources: [...] } }
POST /v1/leads

Capture a visitor's contact details and intent into the tenant's CRM webhook.

curl -X POST https://api.slatech.ai/v1/leads \
  -H 'Content-Type: application/json' \
  -H 'X-Site-Id: {SiteId GUID}' \
  -d '{
        "name": "Jane Doe",
        "email": "[email protected]",
        "message": "Interested in dental whitening pricing"
      }'
GET /v1/landing/{site}/{lang}/{slug}

Fetch a published landing-page payload (FAQ + features + stats) for SEO renderers.

curl https://api.slatech.ai/v1/landing/beauty/en/hair-salons
GET /v1/landing/{site}/sitemap-slugs

List every published (slug, lang, type) tuple for a vertical — feeds dynamic sitemaps.

curl https://api.slatech.ai/v1/landing/med/sitemap-slugs
GET /v1/pricing/{site}/{lang}

Return the live pricing tiers (in tenant currency) для а vertical + language.

curl https://api.slatech.ai/v1/pricing/general/en
GET /v1/public-stats/{siteId}

Public per-site stats — total questions, resolution rate, leads collected, active-since days.

curl https://api.slatech.ai/v1/public-stats/{SiteId GUID}
POST /v1/query/ask-multimodal

Stub returning 501. Reserved для image-upload + question (Q4 2026 — see /en/roadmap/). SDKs probe this endpoint to detect support и fall back к /v1/query/ask.

curl -X POST https://api.slatech.ai/v1/query/ask-multimodal \
  -H 'Content-Type: multipart/form-data' \
  -F 'question=Is this rash an allergic reaction?' \
  -F 'image=@/path/to/photo.jpg'
# Returns 501 today; expected shape lives в the response body.
POST /v1/widget/track

Anonymous visitor analytics — page view, intent classification, dwell time.

curl -X POST https://api.slatech.ai/v1/widget/track \
  -H 'Content-Type: application/json' \
  -d '{ "siteId": "...", "event": "page_view", "url": "https://example.com" }'
Developer FAQ

Auth, rate limits, SDKs, webhooks

Most v1 endpoints accept а Site-Id header (X-Site-Id: {GUID}) that scopes the request к а single tenant's data. Pro-tier и above customers receive an additional bearer token для server-к-server calls; contact [email protected] к provision one. All requests must be HTTPS — plaintext HTTP is rejected at the edge.

Per-site limits: Starter 60 RPM, Pro 600 RPM, Scale 6000 RPM. Headers X-RateLimit-Remaining + X-RateLimit-Reset accompany every response. Bursts up к 2× the limit are tolerated for short windows; sustained over-limit returns 429.

An OpenAPI 3.1 spec ships in the Enterprise tier и is on the public roadmap для Pro. Until then, this page is the canonical reference; example curl commands here are kept in lock-step with production behaviour.

Lead-capture и query-completed events fire к а tenant-configured webhook URL. Signature verification uses HMAC-SHA256 с а per-tenant secret. Idempotency keys are stable for 24 hours — safe к retry on transport failure.

npm @@slatech/bot-sdk и pip slatech are on the platform-evolution roadmap. Until they ship, every endpoint is plain JSON over HTTPS — any HTTP client suffices. Internal helpers in SLAtech.Core/Query (record QueryCommand / QueryResult / QuerySource) document the canonical request/response shapes.

Need а Pro-tier API token?

Server-к-server bearer tokens ship с Pro и above. Email the founder.