Loqva API

Structured access to Loqva's public posts and comments, with the signals that say how good and how current each one is: accepted answers, freshness reviews, votes, edit counts and whether AI was used.

The API isn't open yet. Free keys will be available from Settings → Developer. For licensed access for an organization, email [email protected].

What's included, and what never is

Public posts and comments, licensed CC BY-SA 4.0 by their authors. Never included: members-only content, private messages, personal account data, posts by people under 18, adults-only communities, removed or deleted content, and the posts of members who chose to leave Loqva's data products. The content license lets anyone reuse public posts with credit; what the API adds is clean, current, structured access. See the API Terms.

Tiers

Tier	For	Requests/day	Answers/day	Feed	Snapshots	Price
Free	Personal, educational and research use	1,000	50	—	—	Free
Developer	Building an app, with the change feed	25,000	1,000	Yes	—	Coming soon
Commercial	Showing Loqva content in a commercial product	250,000	10,000	Yes	—	Coming soon
Enterprise	Snapshots, eval datasets and AI training under a signed license	2,000,000	100,000	Yes	Yes	Contact us

Authentication

Send your key in a header (never in the URL):

curl -H "Authorization: Bearer lqv_…" https://loqva.com/api/v1

Every response carries X-Loqva-Tier, X-RateLimit-Limit and X-RateLimit-Remaining (per UTC day). Over a limit you get 429 with Retry-After. Errors look like {"error":{"code":"…","message":"…"}}.

Endpoints

GET /api/v1: your tier, limits and the endpoints.
GET /api/v1/communities?cursor=&limit=: communities and projects.
GET /api/v1/posts?community=&type=&since=&cursor=&limit=: posts, newest first, without comments.
GET /api/v1/posts/{id}: one post with its comments.
GET /api/v1/answer?q=&sources=: the best Loqva sources for a question, each with the passage that answers it.
GET /api/v1/feed?cursor=&limit=: the change feed (Developer and up).
GET /api/v1/snapshots and /api/v1/snapshots/{id}/download: licensed snapshots and eval datasets (Enterprise).

List endpoints return {"data":[…],"next_cursor":"…"}; pass next_cursor back as cursor until it's null.

A post record

{
  "object": "post",
  "schema_version": 1,
  "id": "0b6a…",
  "url": "https://loqva.com/en/t/how-do-i-x/0b6a…",
  "type": "question",
  "title": "How do I X?",
  "body_markdown": "…",
  "community": {
    "slug": "linux",
    "name": "Linux",
    "kind": "community",
    "url": "https://loqva.com/en/c/linux"
  },
  "author": {
    "username": "ana",
    "url": "https://loqva.com/en/u/ana",
    "identity_verified": false
  },
  "created_at": "2026-10-01T10:00:00.000Z",
  "signals": {
    "score": 12,
    "accepted_answer_id": "9c1e…",
    "accepted_answer_counted": true,
    "freshness": "accurate",
    "ai_used": false,
    "staff_pick": false,
    "revisions": 2,
    "comments": 6
  },
  "license": {
    "name": "CC BY-SA 4.0",
    "url": "https://creativecommons.org/licenses/by-sa/4.0/",
    "attribution": "\"How do I X?\" by ana on Loqva, https://loqva.com/en/t/…, licensed CC BY-SA 4.0"
  }
}

accepted_answer_counted is true once an accepted answer passes Loqva's checks (24 hours, no linked accounts). freshness is unreviewed, accurate, outdated or timeless, set by moderators. With comments, each comment has the same kind of signals.

The change feed

Start with ?cursor=latest (from now) or no cursor (replay everything), then keep passing next_cursor. Each event is an upsert with the full post and comments, or a delete. Deletes mean the post was removed, deleted, or its author opted out: the API Terms require you to delete your copy within 30 days. When has_more is false, poll again in a minute or so.

Snapshots and evaluation datasets

Gzipped JSON Lines files with a sha256, one record per line. Full snapshots hold every licensable post with comments. Evaluation datasets hold human-written questions with an accepted, human-written, current answer (and up to three other good answers), optionally limited to questions asked after a date so a model can't have seen them.

Credit

Wherever you show Loqva content, credit the author and link the post and the license. Each record's license.attribution is a ready-made credit line.