Skip to main content
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

Setup

1

Import the Collection

  1. Open Postman
  2. Click Import
  3. Select comind-Private-AI-Platform-API.postman_collection.json
  4. Click Import
2

Import the Environment

  1. Click Import again
  2. Select comind-Private-AI-Platform.postman_environment.json
  3. Click Import
3

Configure Environment Variables

  1. Select “comind Private AI Platform - Local” environment (top-right dropdown)
  2. Click the eye icon to view/edit variables
  3. Update these values:
4

Authenticate

Choose one of these options:
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

1

Check Available Models

Run GET /v1/models to see what’s available.
2

Create Knowledge Base

Run POST /v1/knowledgebases — the KB ID is saved automatically.
3

Upload Documents

Run POST /v1/knowledgebases/{kb_id}/files — upload PDF, DOCX, TXT, CSV files.
4

Query Knowledge Base

Run POST /v1/knowledgebases/query — test with “What are the main topics?”
5

Chat with Knowledge Base

Run POST /v1/knowledgebase/chat/completions — ask questions about your documents.

Stateful Chat Session

Environment Variables

API Endpoint Categories

The collection is organized into these folders:

Supported File Types

Documents: PDF, Word (.docx, .doc), Text (.txt) Spreadsheets: Excel (.xlsx, .xls), CSV (.csv) Presentations: PowerPoint (.pptx) Images: JPG, PNG, GIF, BMP

Troubleshooting

  • Check that pat_token or access_token is set in the environment
  • If using JWT, it may be expired — run the Refresh Token request
  • If using PAT, check it hasn’t been revoked or expired
  • Run “Create Knowledge Base” first
  • Check kb_id is set in the environment variables
  • Check file format is supported (see list above)
  • Verify kb_id is correct
  • Wait for file processing to complete (status: "completed")
  • Lower min_score (try 0.1)
  • Try different query terms