Answers
Wiki Connect answers API
Call policy-constrained answers from your bot with an API key.
6 min read · Updated Jul 2026
Wiki Connect lets your bot ask a question against an AI Application and receive a citation-backed answer, a refusal, or a decision. Create a key on the application, then POST to the answers API. Native Intercom or Zendesk apps are not included.
What you will learn
- How to create and revoke an API key on an AI Application
- How to call POST /api/v1/answers with a Bearer token
- What the response proves: citations, refusal reason, and decision
- Why public chatbots cannot retrieve internal collections
Steps
- 1
Open Wiki Connect on the application
In your workspace, open AI Applications, select the application your bot will call, then open Wiki Connect.
- 2
Create an API key
Name the key after the bot or environment. Copy the secret immediately. Wiki stores only a hash and will not show the secret again.
- 3
Call the answers API
Send a POST to https://wiki.co/api/v1/answers with Authorization: Bearer wk_... and a JSON body that includes question. You may pass audienceId when the application has audiences.
- 4
Read the proof fields
The response includes answer, status, citations, refusalReason, decision, confidenceBand, and applicationId. A refused or unavailable status means no approved source was allowed for that question.
- 5
Keep public bots on public-safe collections
Mark collections Public-safe before a public chatbot can use them. Internal and restricted collections are refused for public-facing application types.
Common issues
- 401 Unauthorized.
- Check the Bearer token. Revoked keys and keys from another application do not authenticate.
- The API refuses a question you can answer in the playground.
- Confirm the collection visibility and the application type. Public chatbots cannot use internal collections.
Related glossary terms
Ready to try it in Wiki?
Start with a Wiki account and set up your Nintendo workspace today.
Was this helpful?