Migrated from Redmine #1511 | Author: Warda Owais
Status: New | Priority: High, I’m very impatient | Created: 2026-01-13
Hello SimplyBook Support,
I am experiencing a serious issue while trying to create bookings using the SimplyBook API.
According to your official documentation, the User API is supposed to work on simplybook.me, however the actual working API endpoint provided by your support team and used in production is simplybook.pro. This mismatch is causing failures in our API integration.
I am sending booking requests to this endpoint:
POST https://user-api-v2.simplybook.pro/admin/bookings
Headers
X-Company-Login: madrcuae
X-Token: [VALID TOKEN]
Content-Type: application/json
Request Body
{
“count”: 1,
“start_datetime”: “2026-12-02 09:30:00”,
“category_id”: 9,
“service_id”: 20,
“client_id”: 242
}
These IDs are coming directly from SimplyBook via API/webhooks:
Category: Physiotherapy session premium (ID: 9)
Service ID: 20
Client ID: 242
Even though all values are valid and exist in the system, the booking is not created and the API returns errors or behaves differently than described in the documentation.
Main issues
The documentation refers to simplybook.me, but the real API runs on simplybook.pro
The same headers, body, and parameters that should work do not behave correctly on .pro
Support-provided endpoints behave differently from the published API documentation
This is blocking our live booking system and webhook-based automation.
Please clarify:
Which domain is officially supported: simplybook.me or simplybook.pro
Why the same request fails on .pro
If any additional permissions, headers, or parameters are required for booking creation
We urgently need a correct and reliable API specification.
Thank you.