What is there now
The HeadHoncho API roadmap starts from what exists: 16 endpoints in 5 groups, Account, Jobs, Job commands, Raw data, Click IDs and conversions. They are on the overview.
How a group gets added
A group arrives when the owner approves it. An endpoint is never built without appearing on this page first, so nothing in the API is a surprise. We plan by group, never one endpoint at a time.
Next
- Leads: the lead stage of a job, tracked calls and the review queue.
- Lookups: statuses, job types and technicians as their own reads.
- Clients: the people jobs are for.
- Job money reads: what a job quoted, collected and left as profit.
Later
- Finance: payments and payouts.
- Reports beyond the Click ID report: the other reports in the app.
- Team: the people who do the work.
- Companies: the client businesses under one login.
- Settings: the words and rules a workspace sets.
- Webhooks: being told when something changes, instead of asking.
Never
These follow from the building-blocks rule on the model: the API gives records, raw rows and single commands, and does not let anyone rebuild the app from outside.
- Boards: screens the app draws.
- Board questions: the questions a board answers.
- Dashboards and widgets: charts and the layouts that hold them.
- Layouts: how the app arranges a screen.
- Automations: rules that act for you.
- Communications: the texts and messages.
- Members: who has a login.
Something you need is not here? Tell support. For what you can call today, see the overview, API keys and the MCP server.