Integration guide
New integrations send reservations with a server-to-server POST. The booking lands in the list of the partner who owns the API keys.
https://app.wow-services.com/api/transfer/new
Where to send the reservation
New integrations send reservations to POST https://app.wow-services.com/api/transfer/new. The booking lands in the list of the partner who owns the API keys.
Keys come from Partner → Settings → API Keys. The same page also has the English documentation, under API Documentation → Insert reservations.
Before the first call
Every request is server-to-server, with Content-Type: application/json and these two headers:
X-Api-Public-Key: <public key>
X-Api-Private-Key: <private key>
The partner is resolved from the public key. wow_company_id in the body is optional. If you send it, it must be your own partner ID, otherwise the response is 403.
The limit is 250 requests per minute.
Minimal request
Only five fields are required inside parsed_data: from, to, date, pickup_time, name.
curl -X POST https://app.wow-services.com/api/transfer/new \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "X-Api-Public-Key: $WOW_PUBLIC_KEY" \
-H "X-Api-Private-Key: $WOW_PRIVATE_KEY" \
-d '{
"parsed_data": {
"from": "Heraklion Airport (HER)",
"to": "Paralos Lifestyle Beach",
"date": "2026-09-08",
"pickup_time": "12:00",
"name": "John Doe",
"phone_number": "+306900000000",
"passengers": "3",
"vehicle_category": "Minivan",
"flight": "BA1234",
"cost": "60.00",
"remaining_cash": "35.00",
"ref_number": "338802109"
}
}'
{
"success": true,
"message": "Transfer created successfully",
"reservation_id": 12345,
"spreadsheet_view_id": 12345,
"code": "338802109"
}
Keep the code and the reservation_id. The code is the key for updates and cancellations. If you do not send ref_number, the system creates a code with the prefix TR.
Fields
| Field | Required | What it does |
|---|---|---|
from
to
|
yes | Pickup and drop-off |
date
|
yes | YYYY-MM-DD. Another format may be stored incorrectly |
pickup_time
|
yes | HH:MM or HH:MM:SS. If it cannot be read, it becomes 00:00:00 |
name
|
yes | Passenger name |
ref_number
|
no | Becomes the reservation code |
phone_number
|
no | With a country code |
passengers
|
no | Default 1. Also used when matching a vehicle |
vehicle_category
|
no | E.g. Minivan. Alias: vehicle_type |
flight
|
no | Flight number. Alias: flight_number |
cost
|
no | Total. Default 0. Also becomes the cash amount if you do not send remaining_cash |
remaining_cash
|
no | What the driver collects on the spot |
eurobank
paypal
|
no | Amounts already paid |
hotel
|
no | If from/to is a general area, it replaces the side that is not an airport, port or station |
infant_seat
|
no | Seat for ages 0–1. Aliases: baby_seat, baby_seat_infant |
child_seat
|
no | Seat for ages 1–4. Aliases: baby_seat_2, baby_seat_child, baby_seat_toddler |
booster
|
no | Seat for ages 4–12. Aliases: booster_seat, baby_seat_booster |
comments
|
no | Notes for dispatch and the driver |
custom_fields
|
no | Free JSON object |
provider_id
|
no | At the top level, not inside parsed_data. It must exist in the providers |
A seat value of 0 is not stored. There is no customer email field. Put the email in comments or in custom_fields.
Without provider_id, the reservation company is written as Transfer API. The status becomes active.
The vehicle is matched first from the partner’s mapping table, then by name, and finally by passenger count. The text you sent always stays in the car column.
Several reservations at once
parsed_data can be an array. Each item becomes its own reservation. Use a unique ref_number per leg, for example 338802109-1 and 338802109-2.
If everything succeeds, the response is 201 with transfers. If some fail after validation has passed, the response is 207: the ones that succeeded are already stored. Resend only the indexes inside failures.
Errors
| Status | Means |
|---|---|
| 401 | The keys are missing or wrong |
| 403 | wow_company_id is not the owner of the key |
| 422 | Validation. Nothing was created |
| 500 | Saving one reservation failed |
The endpoint is not idempotent. Sending the same ref_number twice creates two reservations with the same code. On a timeout, check GET /api/partner/reservations first to see if the reservation was stored, then send it again.
Update and cancel
These two do not ask for API keys. The check uses the original partner of the reservation.
curl -X POST https://app.wow-services.com/api/updatebooking \
-H "Content-Type: application/json" \
-d '{
"code": "338802109",
"wow_company_id": "420",
"parsed_data": { "pickup_time": "14:00", "cost": "75.00" }
}'
curl -X POST https://app.wow-services.com/api/cancelbooking \
-H "Content-Type: application/json" \
-d '{ "code": "338802109", "partner_id": 420 }'