Is there an API?

The API gives you everything the app shows, as JSON, plus the ability to add a site and start research.

Getting a token

1. Open Account settings and find API.
2. Name the token after the tool that will use it and press Create Token.
3. Copy it. It is shown once; we store only a fingerprint. Revoke it from the same place if it leaks.

Send it on every request as a header: Authorization: Bearer lk_.... A token acts as you: anything it starts is charged to your credits, and it can only see your own sites.

Endpoints

All under https://legiitkeywords.com/api/v1. Responses are JSON; errors come back as {"error": "..."} with a 4xx status.

Method and path	What it does
GET /me	Your email and credit balance.
GET /sites	Every site on the account, with its client name.
POST /sites	Add a live site: {"url": "example.com", "name": "…", "market": "US", "client": "…"}. Reads the free profile straight away.
GET /sites/{id}	One site and its recent runs.
POST /sites/{id}/research	Start the research: {"deep": false, "seeds": ["…"]}. Costs credits like the app. Returns the run id; poll it.
GET /runs/{id}	Where a run is: queued, running (with the stage), succeeded, failed.
GET /sites/{id}/plan	The page decisions of the latest finished research: action, title, verdicts, work items, status and published URL. Add ?run={id} for an older run. A locked trial plan returns only the revealed decision, with run.locked true and run.locked_decisions saying how many wait.
GET /sites/{id}/keywords	Every keyword with its status, volume, evidence and cluster. Add ?status=kept to skip the ones set aside. While a trial plan is locked, only the revealed decision's keywords, with run.locked true.
GET /sites/{id}/kb	The latest knowledge base (or ?kb={id}): its plan, its questions with their evidence, and its answers. The text comes only for the answers that go out when you publish: written from your own site or your own words, left ticked, and on a money, health, legal or safety site approved by your named reviewer. For the rest you get the question, its status and note, one sentence on what it needs. 403 on a never-funded account.
POST /sites/{id}/kb	{} prepares the free preview; {"kb_id": "…", "answers": 125, "confirm": true} builds it at one of the sizes the preview offered. Costs credits like the app. Unticking answers and answering questions happen in the app or through the client review link, never through the API.
GET /asks	Every idea on the account (Tools → Keywords for an Idea), newest first, with its state.
POST /asks	Describe one post or video in your own words: {"text": "I want to make a video and a post on …", "market": "US"}, with market one of US, UK, CA or AU (US when left out). 5 credits, like the app: one run reads the idea and finds the keywords, and read_run.id in the reply is that run. Poll GET /asks/{id} until status is done, about two minutes, or until run.status is failed or cancelled. Short of credits, it answers 402. No email is sent when it is ready; a failure still emails you, and the credits come back.
GET /asks/{id}	The idea and its run: the idea's brief (the intent it is judged against and the ways people search for it) and, once done, its result: the primary keyword with its checks and reasons, the other ways to say it, the keywords for each section, why the bigger searches lost, and the related topics. url is the path of the idea's page in the app.

A worked example:

curl -H "Authorization: Bearer lk_..." https://legiitkeywords.com/api/v1/sites
curl -X POST -H "Authorization: Bearer lk_..." -H "Content-Type: application/json" \
  -d '{"deep": false}' https://legiitkeywords.com/api/v1/sites/SITE_ID/research

Limits

Ten active tokens per account. Research started through the API obeys the same rule as the app: two runs in progress per account at a time. Please poll a run no more often than every 30 seconds; a site research run takes 15 to 25 minutes, an idea about two minutes.