Automation and API Beta

Use MotorHangar in Make scenarios

Make (formerly Integromat) can talk to MotorHangar today without a dedicated app: its HTTP module calls our API with your key, and our OpenAPI 3 spec lists every endpoint and field. A native MotorHangar app for Make, with its own modules and triggers, is planned but not built.

Create an API key Plugins and no-code tools OpenAPI 3 spec

How it works

Create an API key in your MotorHangar dealer panel.
In your Make scenario, add the HTTP module's Make a request.
Add a header named Authorization with the value Bearer followed by your mh_ key. Never put the key in the URL.
Call the endpoint you need, for example PUT https://motorhangar.com/api/v1/vehicles/{id} with the car as a JSON body.
For new leads, schedule the scenario and call GET /leads?since= with the time of the last run.

What syncs

Everything the API does: create, update, sell and withdraw cars
A whole stock from a Google Sheet, an Airtable base or your own feed
New leads, by polling

Limitations

Works today, without a native app: you build each request yourself.
No instant trigger: new leads are read by polling until outgoing webhooks exist.
120 calls per minute per key.

Questions about Make

Is there a MotorHangar app in Make?

Not yet; a native app is planned. Today you use Make's HTTP module, which can call any endpoint of our API.

How do I send a whole Google Sheet as my stock?

Read the rows with the Google Sheets module, combine them into one array with an array aggregator, and send it to POST /vehicles/sync with mark_missing_as_sold when the sheet is your complete stock (up to 500 cars per call).

Where should the API key go in Make?

In the HTTP module's header. Never in the URL: URLs end up in logs, and the API only reads the key from the Authorization or X-API-Key header.

Product names belong to their owners. MotorHangar is not affiliated with or endorsed by them, and none of these integrations is listed in their app stores or marketplaces.