This source reads Stack Overflow for Teams, not the public stackoverflow.com. To index public threads, add them as Website pages or upload an export with File Uploads.
Before you start
- A Pro plan or higher, and permission to edit sources in the knowledge base.
- Your team slug: the part after
/c/in your team’s URL. - A Stack Overflow for Teams API token that can read your team’s questions and answers.
Set up
Create an API token
In Stack Overflow for Teams, create an access token with read access to your team.
Add the source
In Kelu, open your knowledge base, go to Sources, click Add source and choose Stack Overflow for Teams. Give it a name, enter the Team slug and paste the API token.
Options
| Option | Required | What it does |
|---|---|---|
| Team slug | Yes | Names your team. |
| API token | Yes | Read access is enough. |
What gets indexed
- One document per question, titled with the question title.
- It holds the tags, the question, and one answer: the accepted answer, or the highest-scored answer if none is accepted.
- A question with no accepted or upvoted answer is indexed without an answer. The source’s Sync history tab lists these.
Sync
Stack Overflow for Teams re-syncs every hour. Click Sync Now on the source page to sync right away.Troubleshooting
- The sync fails with
stackoverflow API status 4xx. The token was revoked or cannot read the team, or the team slug is wrong. Create a new token and update it on the source’s Configuration tab. - The sync fails on a very large team. Kelu reads up to 500 pages of 100 questions. A larger team fails the sync rather than indexing part of it.
- Internal Q&A must stay off public surfaces. Add this source to an internal knowledge base. Nothing in one reaches a public surface.