HelloGrowthCRM Public API & Integration Guide

Quick Start

Base URL

All requests go to our production backend (Supabase Edge Functions) — the same production system that powers the live application at app.hellogrowthcrm.com. It is not a sandbox.

https://jdkqkauiajxyjtvxikmy.supabase.co/functions/v1/integrations-rest

Custom domain (in progress): the same API will also be served from https://api.hellogrowthcrm.com/integrations-rest. Paths, request bodies, and responses are identical — only the hostname changes.

Resources

API Overview

The HelloGrowthCRM Public REST API (integrations-rest, spec 1.1.0) lets you read and write four resources — leads, deals, tasks, and notes — from any app, script, or platform. All requests and responses use JSON and require a Bearer token, except POST /auth/login. Every request is automatically scoped to the logged-in user’s organization (tenant), so you only ever see and change your own organization’s data. All record IDs are UUIDs.

Conventions

List endpoints accept ?limit= (1–100, default 50) and ?offset= (default 0), and return results newest-first (created_at descending). A list response is { "data": [ ... ], "total", "limit", "offset" }; a single record is { "data": { ... } }. Creates return 201 Created; deletes return 204 No Content.

Getting Started (3 Steps)

curl -X POST "https://jdkqkauiajxyjtvxikmy.supabase.co/functions/v1/integrations-rest/auth/login" \
  -H "Content-Type: application/json" \
  -d '{ "email": "you@yourcompany.com", "password": "..." }'

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://jdkqkauiajxyjtvxikmy.supabase.co/functions/v1/integrations-rest/leads?limit=2"

curl -X POST "https://jdkqkauiajxyjtvxikmy.supabase.co/functions/v1/integrations-rest/leads" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "company_name": "Test Co" }'

Token & key security

Send your access token in the Authorization: Bearer YOUR_TOKEN header on every request. Tokens are short-lived (~1 hour); on a 401, log in again or use the Supabase refresh-token grant. For server-to-server or script use, keep credentials secret and never expose them in client-side code.

Resource field reference

Leads: id, tenant_id, lead_name, company_name (required), email_address, phone_number, designation, lead_source, stage_id, deal_value, deal_currency, notes, tags[], website, linkedin_url, created_at, updated_at. Deals: id, tenant_id, name (required), lead_id, stage (enum), value, currency, probability (0–100), expected_close_date, actual_close_date, notes, owner_id, created_at, updated_at. Tasks: id, tenant_id, title (required), description, status, priority, due_date, assignee_id, board_id, completed_at, created_at. Notes: id, tenant_id, lead_id (required), content (required), entry_type, created_at.

Why teams use our API

Teams use the HelloGrowthCRM Public API to sync leads from marketing tools, push deals from quoting systems, automate task creation, and log notes against contacts — all without manual exports. Because the same API powers our official Zapier and Make integrations, you can connect thousands of apps with no code, or call the endpoints directly when you need full control. Every call is tenant-scoped and uses standard JSON over HTTPS.

Related resources

Need implementation help or evaluation resources? Explore our integrations, security documentation, CRM and RevOps blog, and contact page for technical support, trust details, and rollout guidance.