Connect it to what you already run
Push jobs in from anywhere, pull them out to anything, and hear about every event as it happens.
Open platform
Overview
A towing company rarely runs on one system. The motor club has one, the accountant has one, the marketing agency has one. TowSitePros is built so none of them has to be re-typed into it: any job the dashboard can log, another system can log; a system can update, assign and annotate it the same way a dispatcher does; and everything that happens can be delivered to your system as it happens.
What you get
REST API with your own keys
Create a key under Developers, scope it to what that system needs, revoke it when you like. Jobs, units, services, webhooks. JSON in, JSON out, one error shape, an OpenAPI 3.1 document.
Signed webhooks for every job event
Created, assigned, on the way, arrived, done, cancelled, a customer message, a rating, a photo. Each delivery is signed so you can trust it, retried six times over the next 33 hours if your system is down, and logged so you can see it.
GoHighLevel
Connect your location once. Website leads become contacts, bookings land on your calendar, and customer texts can send from your own GoHighLevel number instead of ours.
Zapier, Make, n8n, without code
Any automation tool with a webhook trigger and an HTTP step can drive the API. Log a job from a form, post a Slack message when a truck goes en route, create an invoice when a job completes.
CSV import and export
Bring in your history from your previous system or a batch from a motor club: check the file, then import. Rows with a reference already on a job are skipped, never overwritten. Export any report back out.
Your calendar and your inbox
Bookings made on your site land on your GoHighLevel calendar. Every lead and every job still reaches your email, with the delivery tracked.
Motor clubs and fleet accounts
Push their jobs in with their reference as external_ref, source motor_club or fleet, and the payer set. They get the same tracking page, the same texts, and your reports separate their work from retail.
Up and running in an afternoon
- 1
Create a key
Open Developers, then API keys. Name it for the system it serves and pick the scopes. It is shown once.
- 2
Point a webhook
Add your https endpoint, choose the events, send a test, verify the signature with the secret we give you.
- 3
Ship
POST /jobs from your system, or let Zapier do it. Watch it appear on the dispatch board like any other job.
What it does not do
- We do not connect to motor-club digital dispatch networks directly. Their jobs come in through the API or the import, from whatever system receives them.
- Webhook URLs must be https on a public hostname. We sign every delivery; verify it, and reply within ten seconds.
- API keys are stored only as a hash. Webhook signing secrets are kept so we can sign, and are shown once. If either leaks, revoke or rotate it; we cannot show it again.
No contract, unlimited users and drivers, your domain stays yours.