Skip to content

Developers

Everything in the CRM is an API.

REST, webhooks, MCP and five automation platforms, on every plan, with no developer tier to unlock. Build on the same records Karrie works on.

Read the API docsInteractive reference
First request

One header. One base URL. JSON in, JSON out.

Generate a key under Settings → Integrations → Developer → API keys, send it as a Bearer token, and every list answers with the records under data and a count; a single record comes back as itself.

RequestGET /contacts
curl "https://app.automatenexuscrm.com/functions/v1/api/contacts?limit=25" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"
Response
{
  "data": [ { "id": "…", "email": "jane@example.com", "lead_score": 87 } ],
  "count": 25,
  "total": null
}

The basics

Base URL
https://app.automatenexuscrm.com/functions/v1/api
Auth
Authorization: Bearer <api key>
Format
application/json, HTTPS only
Limits
120 req/min per key; 429 + Retry-After
Surfaces

Six ways in. No developer tier.

  1. 01

    REST API

    Customers, contacts, companies, deals, tasks, notes and invoices over JSON, with tags you can read, set and filter by, plus search, bulk create and update, and export. Bearer-token auth, offset pagination, 120 requests a minute per key, and an OpenAPI schema at /api/schema.

    API overview & auth
  2. 02

    Webhooks

    Subscribe to contact, company, customer, deal, task and form events. Every delivery carries an X-Webhook-Signature header (HMAC-SHA256 over the timestamp and raw body), is retried three times on failure, and is kept in a per-webhook delivery log.

    Webhook guide
  3. 03

    Automation platforms

    Native connectors for Zapier, Make, n8n and Pabbly Connect: trigger on any CRM change or push records in without writing code.

    Integrations directory
  4. 04

    MCP server

    Connect Claude Desktop, Cursor or any MCP client to your CRM with a server key, so your AI tools can read and update contacts, deals and tasks.

    Browse integrations
  5. 05

    Bring your own AI key

    Run the AI layer on your own OpenAI, Anthropic, Google Gemini, Mistral, Groq, Cohere, DeepSeek, Z.ai, OpenRouter, DeepInfra or Fireworks account, or a local Ollama, LM Studio or vLLM server. Keys are encrypted at rest and never leave your workspace.

    Included on every plan
  6. 06

    Test safely

    Dry-run a workflow against a real record without sending anything, run an AI agent in dry-run mode, put Stripe in test mode, and preview the client portal before anyone else sees it.

    Testing without a sandbox
FAQ

The API, answered.

Yes. API access and webhooks are part of the platform on Starter, Growth, Business and Agency. Create keys under Settings → Integrations → Developer → API keys, or under Settings → API keys with an optional expiry. A key reads and writes every resource of the organisation it was created in, and each key can be revoked on its own.

120 requests per minute per API key, counted over the last 60 seconds and the same on every plan. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining, and a 429 includes a Retry-After of 30 seconds.

Each webhook has its own signing secret. Every delivery carries an X-Webhook-Signature header of the form t=<timestamp>,v1=<signature>, where the signature is an HMAC-SHA256 of the timestamp and the raw body, plus X-Webhook-Id and X-Webhook-Event headers. A delivery that does not get a 2xx within ten seconds is retried after one, five and thirty minutes, and every attempt is recorded in the webhook's delivery log.

No official SDK. The API is plain JSON over HTTPS and works with any HTTP client, and GET /api/schema returns an OpenAPI 3.0 document you can import into API tools or a code generator. Zapier, Make, n8n and Pabbly connectors cover most no-code needs.

Reference

Start with the guides.

Your turn

Build on the CRM, not around it.

API keys and webhooks are in every trial from minute one.

Start your 7-day trialTalk to sales