Getting Started

Overview

The Reecall API lets you programmatically manage every resource on the platform — assistants, channels, conversations, hooks, processes, and more. All endpoints follow REST conventions and return JSON.

There are three API services:

Service	Base URL	Purpose
Data API	`https://newprd.reecall.io/data_next`	Core resources — assistants, channels, hooks, exchanges, etc.
Calls API	`https://newprd.reecall.io/calls`	Initiate outbound calls via a channel
Metrics API	`https://newprd.reecall.io/metrics/v1`	Conversation analytics and KPIs

Most integrations only need the Data API.

Authentication

All requests require a Bearer token. Pass your API key in the Authorization header:

Authorization: Bearer {your-api-key}

To get your API key, go to your Reecall dashboard → Settings → API Keys → Create key. See the Authentication guide for full details.

Namespaces

The Data API organizes resources into four namespaces:

Namespace	Resources	What it covers
`core`	projects, users, api-keys, variables, templates, blueprints	Account-level configuration
`conversational`	assistants, channels, exchanges, voices	The runtime — calls and conversations
`ai`	LLMs, STT, TTS, tools, knowledge bases, MCPs	AI model and capability configuration
`automation`	hooks, processes	Post-conversation automation and triggers

Your first call

List your assistants:

curl --request GET \
  --url https://newprd.reecall.io/data_next/conversational/assistants/ \
  --header 'Authorization: Bearer {your-api-key}' \
  --header 'Accept: application/json'

The response includes a Content-Range header with the total count:

Content-Range: items 0-19/42

Filtering and pagination

Every list endpoint supports where, orderBy, limit, page, include, and select query parameters. See the GET Query Parameters page for the full reference.

Quick example — get all active hooks for a specific assistant:

GET /automation/hooks/?where={"assistantId":"<id>"}&limit=20&page=1

Error format

All errors return a standard JSON body:

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Entity not found"
}