Postman Collection
The Co-mind.ai API ships with a complete Postman collection and environment for interactive testing. This guide walks you through setup and common workflows.Files
| File | Description |
|---|---|
comind-Private-AI-Platform-API.postman_collection.json | Complete API collection (130+ endpoints) |
comind-Private-AI-Platform.postman_environment.json | Environment variables with auto-population |
Setup
Import the Collection
- Open Postman
- Click Import
- Select
comind-Private-AI-Platform-API.postman_collection.json - Click Import
Import the Environment
- Click Import again
- Select
comind-Private-AI-Platform.postman_environment.json - Click Import
Configure Environment Variables
- Select “comind Private AI Platform - Local” environment (top-right dropdown)
- Click the eye icon to view/edit variables
- Update these values:
Authenticate
Choose one of these options:
- Option A: Create a PAT (Recommended)
- Option B: Set PAT Directly
- Run “Login” request in the “1. Authentication” folder
- Run “Create API Token” in the “2. API Tokens (PAT)” folder
- The PAT is automatically saved to
pat_token— all requests will use it
The collection uses
pat_token as the default auth for all requests. Auth endpoints and PAT management endpoints override this to use JWT or no auth as appropriate.Example Workflows
PAT Token Setup
RAG Chat Workflow
Stateful Chat Session
Environment Variables
| Variable | Description | Auto-populated? |
|---|---|---|
base_url | API server URL | No |
user_email | Your email | No |
user_password | Your password | No |
pat_token | Personal Access Token | Yes — from Create API Token |
pat_token_id | PAT token ID | Yes — from Create API Token |
access_token | JWT access token | Yes — from Login |
refresh_token | JWT refresh token | Yes — from Login |
user_id | Your user ID | Yes — from Login |
kb_id | Last created KB ID | Yes — from Create KB |
file_id | Last uploaded file ID | Yes — from Upload File |
session_id | Last session ID | Yes — from Create Chat Session |
echo_job_id | Last transcription job ID | Yes — from Async Transcribe |
tenant_id | Tenant/org ID for admin ops | No |
API Endpoint Categories
The collection is organized into these folders:| Folder | Endpoints | Description |
|---|---|---|
| Authentication | 13 | Login, SSO, refresh, registration, password reset |
| API Tokens (PAT) | 6 | Create, list, revoke, rotate tokens, list scopes |
| Knowledge Base Management | 4 | Create, list, get, delete knowledge bases |
| File Management | 3 | Upload, list, delete files in KBs |
| AI Models & Inference | 6 | Models, chat, completions, embeddings |
| Query & Chat (RAG) | 3 | KB queries, KB-enhanced chat, vision+RAG |
| Chat Sessions | 8 | Stateful chat with server-managed history |
| Discovery | 3 | Backends, capabilities, health checks |
| Echo Engine | 16 | Transcription, recordings, TTS |
| Sanitizer Admin | 4 | Security policy management |
| Document Analyzer | 19 | Document extraction and review |
| Researcher | 24 | Search, research, analysis, synthesis |
| Directory Admin | 8 | LDAP/AD configuration |
| Entra Admin | 6 | Azure AD configuration |
| Tenant Admin | 14 | Tenant and sub-org management |
| Audit Logs | 1 | Query audit logs |
Supported File Types
Documents: PDF, Word (.docx, .doc), Text (.txt) Spreadsheets: Excel (.xlsx, .xls), CSV (.csv) Presentations: PowerPoint (.pptx) Images: JPG, PNG, GIF, BMPTroubleshooting
'Unauthorized' error
'Unauthorized' error
'Knowledge base not found'
'Knowledge base not found'
- Run “Create Knowledge Base” first
- Check
kb_idis set in the environment variables
File upload fails
File upload fails
- Check file format is supported (see list above)
- Verify
kb_idis correct
No results from query
No results from query
- Wait for file processing to complete (status:
"completed") - Lower
min_score(try0.1) - Try different query terms

