Slite
DOCS & KNOWLEDGE · FILES & DOCS
Workspace notes, documentation audits, groups, and answers from Ask in the workspace they connected.
Connect Slite with Fabriq Developer
Your user pastes their Slite credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Slite in practice
Slite authenticates with one personal key in an `x-slite-api-key` header, and its own documentation says that key "authorize access to all the user content" — there is no scope, no per-channel restriction and no app-level credential. Search and Ask are scoped to the authenticated user, so an agent sees exactly one person’s view of the workspace and no more.
Scopes that draw scrutiny
x-slite-api-keyThe only credential. Slite’s wording: "Every call to our public API has to be authenticated with a personal API key, generated in your settings. This API key authorize access to all the user content."
Rate limits
- Base URL is https://api.slite.com/v1.
Worth knowing
- The key "will only be displayed once, so make sure to save it" — recovery means minting a new one and revoking the old.
- Deleting a note takes its children with it, and the reference says so in the plainest possible terms: "Delete a note and its children by id. !!! It’s irreversible !!!"
- Ask is asynchronous. `GET /ask` can return a `processing` answer plus a `threadId`, and you poll the thread endpoint to read the question/answer rounds back.
- Because search and Ask are restricted to the authenticated user, two agents holding two different users’ keys will legitimately get different answers to the same question.
Checked against Authentication — get your API key (2026-09-29), Slite API documentation index (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Slite behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.