Skip to main content
The Nixflex API is REST over HTTPS. All requests use JSON. Authentication is via Bearer token (see Authentication).

Base URL

All endpoints in this reference are relative to this base URL.

Versioning

The current version is v1. All paths are prefixed /v1/. When v2 is released, v1 will continue working unchanged for at least 12 months. Breaking changes always live behind a new version.

Authentication

Every request requires an Authorization header:
The colon between key_id and key_secret is required. See Authentication for details.

Request format

POST, PUT, and PATCH requests must include Content-Type: application/json and a JSON body. GET requests use query parameters where applicable.

Response format

All responses are JSON. Success responses return the resource directly:
Error responses follow a consistent envelope (see Errors):

Result limits

Nixflex does not currently support offset-based pagination. Each list endpoint returns a fixed set of results:
GET /v1/calls returns only the 50 most recent calls and cannot reach older records. To keep full call history, subscribe to the call.completed webhook and store each call in your own backend as it arrives.

Resource list

Agents

Create and manage AI agents (prompt, voice, behaviour).

Calls

List, fetch, and trigger calls. Outbound + batch.

Phone numbers

Import numbers from Twilio or Telnyx and attach them to agents.

SMS

Send individual messages and bulk campaigns.

Account

Manage API keys and view usage.

OpenAPI specification

The whole API is described in a machine-readable OpenAPI 3.1 document:
Full URL: https://docs.nixflex.com/api-reference/openapi.json Use it to:
  • Import every endpoint into Postman or Insomnia - one paste and each request is ready to send, fields included.
  • Generate a client in your language - run any OpenAPI generator against it for Python, Go, PHP, Ruby, Java, or C#. For Node.js, use the official SDK instead.
  • Give an AI coding assistant the real shape of the API - tools that read a spec write correct calls instead of guessing field names.
The spec covers authentication, every request and response schema, and the shared error envelope. A few objects with long field lists stay open in the spec and link to the page that documents them in full.

Status codes

Idempotency

Mutation endpoints (POST, PUT, PATCH, DELETE) accept an optional Idempotency-Key header for safe retries:
Requests with the same key within 24 hours return the original response. Safe to retry on network failures.