Evimarko API for developers
Connect your website, form, bot or accounting to Evimarko: read services, clients and bookings, book a free time and get an event the moment something happens in the studio.
Start in 3 steps
1
Get a key
The studio owner opens Settings → Integrations → For developers and presses “Create key”. The key is shown once — copy it.
2
Make the first request
Send the key in the Authorization header. GET /me answers with the studio the key belongs to.
3
Subscribe to events
Give us your https address in POST /webhooks — new bookings and status changes will come to it by themselves.
curl https://evimarko.com/api/v1/me \
-H "Authorization: Bearer dos_YOUR_KEY"
Key, rights and limits
Every request carries the key in the header “Authorization: Bearer dos_…”. One key works for one studio only; it never sees another studio. The owner can revoke a key at any moment.
- “Only look” — read data and subscribe to events.
- “Look and add” — also create clients and bookings.
Limits: 120 requests a minute per key and 30 a minute for creating clients, bookings and webhooks. Over the limit the answer is 429 with a Retry-After header.
What the API can do
All requests and answers are JSON. Base address: https://evimarko.com/api/v1
OpenAPI 3.1 specification (JSON) →
Studio
| GET | /me | The studio of the key (also the way to test a key) |
Services
| GET | /services | List services |
| GET | /services/{id} | Get a service |
Clients
| GET | /clients | List clients or find one by phone |
| POST | /clients | Create a client |
| GET | /clients/{id} | Get a client |
Cars
| GET | /clients/{id}/vehicles | Cars of a client |
| GET | /vehicles | List cars |
| GET | /vehicles/{id} | Get a car |
Bookings and orders
| GET | /orders | List bookings and orders |
| GET | /orders/{id} | Get a booking or order (its status) |
| GET | /slots | Free times of a day |
| POST | /bookings | Book a free time |
Webhooks
| GET | /webhooks | List webhooks |
| POST | /webhooks | Subscribe to events (REST hook) |
| DELETE | /webhooks/{id} | Unsubscribe |
Accounting (read only)
| GET | /payments | List payments |
| GET | /payments/{id} | Get a payment |
| GET | /materials | List materials |
| GET | /materials/{id} | Get a material |
| GET | /stock-movements | List stock movements |
| GET | /stock-movements/{id} | Get a stock movement |
| GET | /expenses | List expenses |
| GET | /expenses/{id} | Get an expense |
Book a free time
A booking through the API follows the same rules as the studio’s own booking page: only free times, only services the studio opened for online booking.
# 1. Free times of the day
curl "https://evimarko.com/api/v1/slots?date=2026-11-21&services=12" \
-H "Authorization: Bearer dos_YOUR_KEY"
# → {"date":"2026-11-21","timezone":"Europe/Sofia","duration_minutes":120,"slots":["10:00","12:00","14:00"]}
# 2. Book one of them
curl -X POST https://evimarko.com/api/v1/bookings \
-H "Authorization: Bearer dos_YOUR_KEY" -H "Content-Type: application/json" \
-d '{"services":[12],"date":"2026-11-21","time":"10:00","name":"Maria","phone":"+359 88 123 4567","make":"Kia","model":"Sportage"}'
# → 201 {"data":{"id":345,"number":118,"status":"scheduled","starts_at":"…","client_url":"…"},"client_created":true,"deposit_url":null}
- The time is the studio’s own clock (see “timezone” in GET /me). You can send “starts_at” with a time zone instead of date and time.
- A known phone number books the existing client; a new one creates a client.
- If the time was taken a second ago, the answer is 422 — ask for free times again.
- The staff get their usual notice about the booking, the client gets the usual confirmation.
Webhooks: events as they happen
We send a POST with JSON to your address for each event you choose. This is how triggers in Zapier, Make, n8n and Pipedream work.
curl -X POST https://evimarko.com/api/v1/webhooks \
-H "Authorization: Bearer dos_YOUR_KEY" -H "Content-Type: application/json" \
-d '{"url":"https://example.com/evimarko","events":["booking.created","order.ready"]}'
# → 201 {"data":{"id":7,"url":"…","events":[…],"secret":"…"}}
| booking.created | A new booking — from the booking page, a bot, the API or the CRM |
| order.status_changed | The status of an order changed (with the previous status) |
| order.ready | The car is ready |
| order.delivered | The order is delivered to the client |
| payment.created | A payment was recorded |
| material.purchased | A material purchase |
| expense.created | An expense |
| client.created | A new client |
Check that the event is from us
Every delivery has the header X-Evimarko-Signature: “sha256=” plus the HMAC-SHA256 of the raw body with the secret you got when subscribing. Compare it before trusting the data.
// Node.js
const crypto = require('crypto');
function isFromEvimarko(rawBody, header, secret) {
const expected = 'sha256=' + crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
return header.length === expected.length && crypto.timingSafeEqual(Buffer.from(header), Buffer.from(expected));
}
// PHP
$ok = hash_equals('sha256=' . hash_hmac('sha256', $rawBody, $secret), $_SERVER['HTTP_X_EVIMARKO_SIGNATURE'] ?? '');
- Answer 2xx within 10 seconds. Otherwise we retry after 1, 5 and 30 minutes, then 2 and 6 hours.
- The “id” of a delivery stays the same on a retry — use it to skip duplicates.
- Answer “410 Gone” to unsubscribe at once. After 30 failed deliveries in a row we switch the webhook off; the owner can switch it on again in Settings.
- Only public https addresses are accepted. Local and internal addresses are refused.
Errors
An error is always JSON: {"message": "…"}; for 422 there is also “errors” with messages per field.
| 401 | No key, a wrong key or a revoked key. |
| 402 | The API is not included in the studio’s plan. |
| 403 | The studio has no access, or a read-only key tries to create something. |
| 404 | No such row in this studio. |
| 422 | The data did not pass the check, or the time is not free. |
| 429 | Too many requests. Wait as many seconds as Retry-After says. |
Ready-made apps
No code needed: connect Evimarko to thousands of other services in an automation tool.
Zapier
SoonTriggers: new booking, status changed, car ready, order delivered, new client. Actions: create a client, create a booking, find a client, find free times.
Make
SoonInstant triggers on studio events and modules for clients, services, free times, bookings and orders.
n8n
SoonCommunity node n8n-nodes-evimarko: an Evimarko node with actions and an Evimarko Trigger node on webhooks.
Pipedream
SoonSources for studio events and actions for clients and bookings.
What the API never does
- It takes no payments and moves no money.
- It deletes nothing in the studio: no clients, no cars, no orders.
- It gives no access to another studio — a key belongs to one studio.
- We store only a fingerprint of the key, not the key itself. Lost it — create a new one and revoke the old.
Need help?
Write to us — we will help to connect. Telegram
No Evimarko account yet? Try the CRM for free and create an API key in two minutes.