Skip to main content
Connic
Reference

REST API

Access your Connic project programmatically with API keys: query runs, manage retrieval, pull cost data, and manage deployments. To run agents in response to events, use a connector.

Last updated

Overview

Connic exposes a REST API that lets you interact with your project outside of the dashboard. Use it to pull run results into external monitoring, manage your retrieval programmatically, and query cost data for billing dashboards.

All API requests are authenticated with project-scoped API keys and rate-limited per project. The full endpoint reference includes request and response schemas plus example requests. Open API endpoints.

To start an agent from HTTP, queues, email, schedules, or your own application, use a connector. The REST API is for managing and observing your project.

Authentication

API requests are authenticated using API keys. Each key is scoped to a single project and can only access endpoints within that project. Pass the key as a Bearer token in the Authorization header:

HTTP header
Authorization: Bearer cnc_your_api_key

Create and manage API keys in Project Settings → API Keys & MCP Auth. Keys start with the cnc_ prefix and are shown only once when created. Store them securely.

Security
Never commit API keys to version control or expose them in client-side code. For CI/CD, store them as encrypted secrets (e.g. CONNIC_API_KEY).

API Key Permissions

Each API key uses the same action-level project permissions shown in Team & Permissions. Keep all available permissions selected or choose individual permissions, then edit that selection at any time.

Permission Model

The permission picker shows API-supported permissions available to the account creating or editing the key.

ConceptDetails
All permissionsThe default. Includes every API-supported permission available to the key owner.
Individual permissionsIncludes only the selected action-level permissions and may be empty.
Owner permissionsA key never exceeds its owner's project access, even if the key has broader permissions selected.
EditingThe key owner can change its name and permissions. Project members with permission to delete API keys can revoke it.
API key permissions add a credential-specific restriction on top of the owner's project permissions. They can narrow access, never widen it.

Rate Limiting

API requests are rate-limited per project. All API keys belonging to the same project share the limit. When the limit is exceeded, the API responds with:

ResponseDetails
Status Code429 Too Many Requests
Retry-After HeaderNumber of seconds to wait before retrying

If you need higher limits, contact the Connic team.

Quick Examples

Get Run Details

terminal
curl https://api.connic.co/v1/projects/{project_id}/runs/{run_id} \
  -H "Authorization: Bearer cnc_your_api_key"

Upload Text to Retrieval

Retrieval endpoints require an environment_id query parameter to scope the request to a specific environment.

terminal
curl -X POST "https://api.connic.co/v1/projects/{project_id}/retrieval/text?environment_id={env_id}" \
  -H "Authorization: Bearer cnc_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Your document text here...",
    "namespace": "docs.api",
    "entry_id": "my-custom-id"
  }'

Error Responses

The API uses standard HTTP status codes. Error responses include a JSON body with a detail field describing the issue.

CodeMeaning
401Missing or invalid API key
403Key lacks permission for this endpoint, or the endpoint is not part of the public API
404Resource not found
429Rate limit exceeded. Check the Retry-After header.
500Internal server error
API endpoints

Explore all endpoints with full request/response schemas and example code snippets.

Open API endpoints