API Overview

The Kasar API gives you programmatic access to your CRM data. It follows REST conventions, returns JSON, and uses bearer token authentication.

Base URL

https://kasar.app/api/v1

All requests must use HTTPS. Your organization is identified by the API token — no subdomain needed.

Endpoints

Records

Tasks

Notes

Schema

Pipelines

Search

Aggregations

Activity

Inbox

Bulk Operations

Import / Export

Users

Duplicates

Response Format

All successful responses return JSON with a consistent structure.

Single record:

{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "first_name": "Alice",
    "last_name": "Martin",
    "email": "alice@example.com",
    "created_at": "2025-01-15T10:30:00Z"
  }
}

Paginated list:

{
  "data": [
    { "id": "...", "first_name": "Alice", "last_name": "Martin" },
    { "id": "...", "first_name": "Bob", "last_name": "Dupont" }
  ],
  "total": 142,
  "nextCursor": "eyJpZCI6IjU1MGU4NDAw..."
}

Use the nextCursor value as a query parameter to fetch the next page of results. When nextCursor is null, you have reached the last page.

Error Format

Errors return an appropriate HTTP status code and a JSON body:

{
  "error": true,
  "code": "VALIDATION_ERROR",
  "message": "Field 'email' must be a valid email address"
}

Error Codes

Rate Limits

The API enforces rate limits per token. When you exceed the limit, the API returns HTTP 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying.

Design your integrations to handle 429 responses gracefully with exponential backoff.

CORS

The API sets appropriate CORS headers for browser-based requests. If you are calling the API from a frontend application, requests from your configured domain are allowed automatically. For server-to-server integrations, CORS does not apply.

Endpoint Reference