/v1. This API is designed for automation tools such as Zapier, Make, and n8n.
No-code endpoints use REST methods, query strings for filters, and JSON request bodies for create and update actions.
Base URL
Authentication
Create an API key in Hellotracks under More -> API & Integrations. Send the key in theAPI-Key header.
Response Format
List and action responses return adata object. Most connector endpoints return an items array inside data.
data.items before returning records to Zapier, Make, or n8n.
Error Format
Failed requests may return anerror object. Treat error.message as the user-facing failure reason.
Authentication Test
Use this endpoint to validate that an API key works.Jobs
Watch or list jobs
UseGET /jobs for polling triggers, job dropdowns, and lookup flows.
Examples:
Get a job
UseGET /jobs/{id} when you already have the Hellotracks job ID.
Create a job
UsePOST /jobs to create a job. If externalId matches an existing job, Hellotracks uses it as a stable dedupe key and may update the existing job.
Update a job
UsePATCH /jobs to update an existing job. Send the Hellotracks job id in the JSON body and include only the fields you want to change.
Archive a job
Use archive when the job should no longer appear in active schedules but should remain recoverable in Hellotracks.Delete a job
Use delete only for disposable or intentionally removed jobs.Job Object
Connector responses include stable job fields.Members
Use members for assignment lookups, dropdowns, and exact-match searches.
Example:
Connector Behavior
Zapier, Make, and n8n use the same production/v1 contract: