Everything here needs knowledge:read, and only returns what the key's owner can open in the app. To write documents, see Documents.
Answer a question from your documents
- 1
Search
POST /v1/knowledge/searchfinds the passages that best answer a question. Ask a whole question: search matches meaning, not just words.curl -X POST https://developers.playbookops.ai/v1/knowledge/search \ -H "Authorization: Bearer $PLAYBOOKOPS_API_KEY" -H "Content-Type: application/json" \ -d '{"query": "How do we handle refunds over $500?"}'{ "data": [ { "document_id": "…", "title": "Refunds and credits", "passage": "Refunds over $500 need a manager's approval…", "similarity": 0.87, "playbook_name": "Support", "url": "https://app.playbookops.ai/playbooks/…" } ], "credits_used": 1 } - 2
Read the document
If the passage isn't enough,
GET /v1/documents/DOCUMENT_IDreturns the whole document as Markdown. Documents over 24,000 characters are cut off, withtruncated: true; add?full=truefor all of it. - 3
Find someone to ask
When the documents don't cover it,
POST /v1/knowledge/who-knowswith a topic returns the people who know about it, and why.curl -X POST https://developers.playbookops.ai/v1/knowledge/who-knows \ -H "Authorization: Bearer $PLAYBOOKOPS_API_KEY" -H "Content-Type: application/json" \ -d '{"topic": "payroll"}'
Each call uses 1 AI credit from your organization, and says so in credits_used. Everything else on this page is free. See limits and credits.
Browse
GET /v1/playbooks?search=onboardinglists playbooks, with how many documents each has.GET /v1/content?kinds=document&playbook_id=PLAYBOOK_IDlists documents, files, flowcharts, videos and more, newest first.
Reference
| Action | Endpoint | MCP tool |
|---|---|---|
| Search | POST /v1/knowledge/search | search_knowledge |
| Who knows | POST /v1/knowledge/who-knows | who_knows |
| Read a document | GET /v1/documents/{id} | read_document |
| Create a document | POST /v1/playbooks/{id}/documents | create_document |
| Change a document | PATCH /v1/documents/{id} | update_document |
| Playbooks | GET /v1/playbooks | list_playbooks |
| Content | GET /v1/content | list_content |
Every parameter is in the API reference.