DJC AI API
Documentation menu

Start here

Guides

API reference

More

Start here

Introduction

DJC AI API lets your own software — scripts, integrations and AI agents — work inside your DJC AI workspace the way you do in the app.

What it is

Everything you build in the app lives in a workspace (your organisation). A personal API token lets code actas you in that workspace, over plain JSON HTTPS. You decide, per token, whether it may only read or alsowrite, and which resources it can touch. Tokens are created, revealed and revoked in the app; nothing about them lives on this site.

  • Least privilege by default. A read token can never change anything — not even by accident.
  • One token for several resources. Give an agent Knowledge · read & write and Workflows · read in a single credential.
  • Your credits, your account. Work that calls a model (Ask, extraction, LLM nodes) is charged to your balance in that workspace, exactly as if you had clicked it in the app.

What you can reach today

Knowledge

Q&A knowledge bases

List and create bases. Search with hybrid vector + keyword retrieval, ask for a grounded answer, add and edit entries, import in bulk, submit text and documents for AI extraction, and see the questions your base could not answer.

https://api.simplynice.ai/api/ai/knowledge

Workflows

Simple Flow automations

List and create flows. Read and rebuild graphs, add and edit nodes and edges, test one node with sample data, run the flow and read a per-node log. The canvas in the app updates live as you edit.

https://api.simplynice.ai/api/ai/simple-flow

More of the app will open up over time; each new resource appears here with its own guide and reference, and as a new scope on the token page.

Tokens act as you

A token sees what you see: every knowledge base in the workspace, and the flows you own there. It cannot reach another workspace, and it stops working the moment you revoke it or it expires.

How it fits your system

  1. Your app → API. https://api.simplynice.ai with Authorization: Bearer djc_…. Read, write, run.
  2. Your flows → your channels. Flows you build through the API run on the same engine as the canvas — including WhatsApp triggers and replies configured in the app.
  3. AI agents. Hand an agent the credentials JSON from the token page and a link to this documentation; every response carries the ids it needs for the next call.

Where to go next

  • Quickstart — create a token, call /me, make your first read and write. Five minutes.
  • Authentication & scopes — what read and write mean per resource, expiry, revocation.
  • Core concepts — workspaces, credits, the ids you will pass around.
  • API reference — every endpoint with samples and the scope it needs.