Lookio Docs
Lookio websiteOpen Lookio
DevelopersIntegrations

Integrations

Call a Lookio assistant from n8n, Make, Zapier or any tool that sends HTTP requests, with an API key, one request, and the answer with its sources.

Any tool that sends HTTP requests can ask a Lookio assistant. You need an API key, the id of the assistant, and one POST request.

flowchart LR T["New ticket<br/>(help desk, form, email)"] --> W["Your automation<br/>n8n, Make, Zapier"] W -- "POST /v1/assistants/{id}/query" --> L["Lookio"] L -- "answer, citations, credit_cost" --> W W --> D["Draft reply<br/>in the help desk"]
A typical automation: a support ticket gets a draft answer

Before you start

Create an API key

In the app, open Developer tools, then Create key. Choose the Ask questions preset. Copy the key: Lookio shows it once. See API keys.

Copy the assistant's id

Open the assistant. Its id, such as ast_kw9tvh2ze2ar, is at the top of its sheet. The API button gives the whole request.

The request

Value
MethodPOST
URLhttps://api.lookio.app/v1/assistants/ASSISTANT_ID/query
HeaderAuthorization: Bearer sk_live_…
HeaderContent-Type: application/json
Body{"question": "…", "end_user": "…"}

The answer is in data.answer, the passages in data.citations and the price in data.credit_cost. Use end_user to name the person who asks, for example the customer id of a ticket. You then find their conversations in Logs.

In your tool

Add an HTTP Request node.

  1. Method: POST. URL: the URL above.
  2. Authentication: Generic credential, Header Auth. Name Authorization, value Bearer sk_live_….
  3. Send Body: on, JSON, with:
JSON
{
  "question": "{{ $json.subject }}\n\n{{ $json.body }}",
  "end_user": "{{ $json.customer_id }}"
}

The next node reads {{ $json.data.answer }}.

Add an HTTP module, Make a request.

  1. URL: the URL above. Method: POST.
  2. Headers: Authorization with Bearer sk_live_….
  3. Body type: Raw, Content type JSON, and the body with your question.
  4. Turn on Parse response. The next modules read data.answer and data.citations.

Add a Webhooks by Zapier action, Custom Request.

  1. Method: POST. URL: the URL above.
  2. Data: the JSON body with your question.
  3. Headers: Authorization with Bearer sk_live_…, and Content-Type with application/json.

The next steps read data__answer.

Terminal
curl https://api.lookio.app/v1/assistants/ASSISTANT_ID/query \
  -H "Authorization: Bearer $LOOKIO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: ticket-4821" \
  -d '{"question": "Can I change my plan mid-month?", "end_user": "cus_1042"}'

Good practice

Send an Idempotency-Key

Automation tools retry after a timeout. Send an Idempotency-Key made from the event, such as the ticket id. Then a retry is not charged twice. See Conventions.

Give the request time

An answer takes a few seconds, more in Deep mode. Set the HTTP timeout of your tool to 60 seconds or more.

Keep a thread with conversation_id

For a follow-up in the same ticket, send the previous answer’s conversation_id. Lookio reads the history itself. See Conversations and end users.

Forward your agents' thumbs

If a person reviews the draft, send their thumbs up or down to Lookio. It shows in Logs, next to the answer. See Feedback on answers.

Limit the key

Give the automation its own key, with the Ask questions preset and only the assistants it needs. You can then revoke it alone.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Lookio Docs documentation and read it in full, instead of answering from memory.

https://lookio.app/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://lookio.app/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.