Developer API

Every answer your team gets,
your code can get too

One API call. A cited answer with confidence scores, source documents, and freshness indicators. Same permissions. Same Trust Panel. Same everything.

Get API access Read the documentation

Try it yourself

Send a request and watch the cited response stream back.

POST

curl -X POST https://api.internalwiki.com/v1/ask \
  -H "Authorization: Bearer iw_key_..." \
  -H "Content-Type: application/json" \
  -d '{"question": "What is our parental leave policy?"}'

Response

// Click Run or wait for auto-play...

What you get back

Every response includes the answer, citations, confidence, and timing. Hover any field to understand it.

{
"answer": "Full-time employees are entitled to..."
"citations": [
{
"index": 1,
"document": "Employee Handbook v4.2",
"section": "Section 4.2 — Parental Leave",
"passage": "All full-time employees are...",
"confidence": 0.94,
"freshness": "current"
}
],
"confidence": 0.94,
"sources_searched": 3,
"sources_cited": 1,
"latency_ms": 820
}

Hover over a field in the JSON to see what it does

Four endpoints. That's it.

The API is deliberately simple. One endpoint to ask questions. Three to manage everything else.

POST/v1/ask

The main endpoint

Send a question, get a cited answer. Supports optional parameters for max_sources, confidence_threshold, and response_format.

GET/v1/sources

List connected data sources

List all connected data sources with their sync status, document count, and last sync timestamp.

GET/v1/usage

Usage statistics

Usage statistics for the current billing period: questions asked, sources queried, average latency, average confidence.

GET/v1/health

Health check

Returns API status, current latency percentiles, and any ongoing incidents.

Works with any language

If it can make an HTTP request, it can use InternalWiki.

1curl -X POST https://api.internalwiki.com/v1/ask \2  -H "Authorization: Bearer iw_key_..." \3  -H "Content-Type: application/json" \4  -d '{5    "question": "What is our parental leave policy?",6    "max_sources": 5,7    "confidence_threshold": 0.38  }'

What to build with it

Slack bot

Build a /ask slash command that answers questions directly in Slack. When someone types /ask What's our expense policy?, the bot returns the cited answer in the channel. Source links open directly in Google Drive or SharePoint.

Help desk integration

Wire InternalWiki into your support system. When a ticket comes in, auto-suggest a cited answer from your knowledge base. Support agents verify with one click instead of searching through 6 different tools.

Onboarding flow

Embed a knowledge widget in your onboarding platform. New hires ask questions as they go through training — 'What's the dress code?' 'How do I submit expenses?' — and get instant cited answers without interrupting the team.

Compliance automation

Build a pipeline that checks claims in documents against your policy library. 'This contract says 12 weeks of leave' → InternalWiki checks → 'Current policy is 16 weeks [1].' Flag discrepancies automatically.

Authentication & rate limits

Authentication

Bearer token in the Authorization header. Generate API keys in your workspace settings. Keys can be revoked instantly. All requests over HTTPS.

Bearer token authentication
Keys generated in workspace Settings
Instant revocation
All requests over HTTPS
Scoped to workspace — one key per workspace

Authorization: Bearer iw_key_...

Rate limits by plan

Plan	Requests/mo	Rate	Price
Free	100	10/min	$0
Team	10,000	100/min	$18/user/mo
Enterprise	Custom	Custom	Contact us

Need higher limits? Contact us →

Start building

Get your API key and send your first request in under a minute.