Your workspace, driven by API · API 2026-08
Query and grow your Knowledge bases, build and run Simple Flow workflows — from scripts, integrations and AI agents — with one personal token scoped to exactly what you allow.
curl -X POST "https://api.simplynice.ai/api/ai/knowledge/bases/$KB_ID/ask" \
-H "Authorization: Bearer $DJC_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "query": "How long is the X200 warranty?" }'
# → { "answer": "Two years from purchase (parts and labour); batteries one year.",
# "hits": [ { "subject": "Warranty", "question": "What is the warranty on the X200?", … } ] }curl -X POST "https://api.simplynice.ai/api/ai/simple-flow/flows" \
-H "Authorization: Bearer $DJC_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "Translate to Chinese",
"nodes": [
{ "id": "node1", "type": "trigger", "config": { "sampleData": { "text": "Good morning" } } },
{ "id": "node2", "type": "llmChain", "config": { "prompt": "Translate to Chinese: {{text}}" } },
{ "id": "node3", "type": "output" }
],
"edges": [ { "source": "node1", "target": "node2" }, { "source": "node2", "target": "node3" } ]
}'What you get
Built for CRMs, support desks, content pipelines and AI agents that need your knowledge and automations behind them.
Create a personal token in the app, pick Read only or Read & write, and tick the resources it may touch. Revoke it the moment it's not needed.
Search a base with hybrid vector + keyword retrieval, or Ask for a grounded answer — exactly what your flows see at runtime.
Add Q&A pairs, import a spreadsheet's worth in one call, or submit raw text and documents and let the AI extract the pairs.
List, create and edit Simple Flow graphs — nodes, edges, configs — from a script or an AI agent. The canvas updates live.
Try one node with sample items before you wire it in, then run the whole flow and poll a structured log of every step.
Every endpoint answers with the ids and shapes an agent needs next. Point Claude, ChatGPT or your own agent at the reference and go.
How it works
In the app: avatar menu → API → Create token. Choose the access level and resources.
Confirm the token works and read back the scopes it holds.
GET /bases or GET /flows — or create a new one with a write token.
Search and ask, add entries, edit nodes, execute a flow. Every call is plain JSON over HTTPS.
API reference
Parameters, request and response samples, the scope each call needs and the exact error codes — no guesswork. More resources are added as they open up.
Create a token in the app, call /me, and make your first request before your coffee cools.