The Postman Collection is being shared alongside our developer documentation so teams always start from the latest request examples, auth patterns, and webhook setup guidance.
Request examples for core CRM resources, bearer-auth setup, and a clean starting point for testing the API from Postman or compatible tools.
Review the docs first, then reach out if you need the latest collection or support mapping endpoints into your integration workflow.
The collection mirrors the REST API surface documented at /docs: pre-built requests for the core CRM resources, organised into folders so you can run a realistic end-to-end flow in minutes rather than hand-writing curl commands.
List, create, update, and search requests for leads and contacts — the entities most integrations touch first, e.g. pushing web-form submissions into the pipeline.
Requests to read deal records and move them between stages, useful for syncing won/lost status into billing or reporting systems.
Create follow-up tasks and log activities programmatically — the building blocks for connecting external schedulers or support tools to rep workflows.
Sample payloads and configuration guidance for subscribing to events, so your system reacts when a lead is created or a deal changes stage.
Generate an API key from Settings → API Keys inside your HelloGrowthCRM workspace. Trial and free accounts can create keys, so you can test before paying.
Import the collection into Postman (or any compatible client such as Insomnia or Bruno) and set the api_key collection variable. Every request inherits the Authorization: Bearer header from there — no per-request editing.
Run the GET leads request first. A 200 response with your workspace data confirms the key works; from there, duplicate any folder request and adapt it to your integration.
Typical integration patterns we see teams prototype with this collection: syncing leads from a custom website or landing-page builder, pushing closed-won deals into an invoicing system, mirroring contact updates into a data warehouse for BI, and triggering internal Slack or email alerts off webhook events. Rate limits scale with plan tier — heavy production sync volumes belong on a paid plan sized to your request rate.
Keep keys server-side only, rotate them periodically, and revoke immediately if one leaks. If you hit an endpoint question the docs don't answer, or need the most recent collection export, write to the team via the contact page— include what you're building and we'll point you at the right resources. Security posture for the API and platform overall is documented on the security page.