cancelBooking failing!

API General
1

hi

I keep getting a 500 error when cancelling a booking via the user API (admin).
I’ve even reduced the problem to API calls within the Insomnia API client and still it is failing. I’ve had one success and then failures thereafter with very little different except the booking ID. Please help

3

Hi, please provide RAW HTTP request.

5

This seems like a public forum… I’ll try to remove the sensitive bits:
Preparing request to https://user-api.simplybook.me/admin/

  • Current time is 2026-02-17T11:21:28.161Z
  • Enable automatic URL encoding
  • Using default HTTP version
  • Enable SSL validation
  • Found bundle for host: 0x11c096d0c80 [can multiplex]
  • Re-using existing connection #47 with host user-api.simplybook.me
  • Connected to user-api.simplybook.me (142.44.140.176) port 443 (#47)
  • h2h3 [:method: POST]
  • h2h3 [:path: /admin/]
  • h2h3 [:scheme: https]
  • h2h3 [:authority: user-api.simplybook.me]
  • h2h3 [content-type: application/json]
  • h2h3 [user-agent: insomnia/10.3.0]
  • h2h3 [x-company-login: futuremediabeta]
  • h2h3 [x-user-token: …376f]
  • h2h3 [accept: /]
  • h2h3 [content-length: 124]
  • Using Stream ID: 3 (easy handle 0x11c0a525800)
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):

POST /admin/ HTTP/2
Host: user-api.simplybook.me
content-type: application/json
user-agent: insomnia/10.3.0
x-company-login: futuremediabeta
x-user-token: …376f
accept: /
content-length: 124

  • TLSv1.2 (OUT), TLS header, Supplemental data (23):

| {
| “jsonrpc”: “2.0”,
| “method”: “cancelBooking”,
| “params”: [
| 872
| ],
| “id”: “3c17a847-109b-446a-b7f2-9405624ae55f”
| }

  • We are completely uploaded and fine
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 500
< server: nginx
< date: Tue, 17 Feb 2026 11:21:28 GMT
< content-type: text/html; charset=UTF-8
< content-length: 0
< x-iplb-request-id: 29C152DB:E4AB_8E2C8CB0:01BB_69944F33_4190DA7:2EC2FF
< strict-transport-security: max-age=15768000
< x-iplb-instance: 65803

6

Hi, could you please try again? It should work now.

7

it did work! can you help me understand. I’ve had a success earlier as well and now again (see image below). is it something on my side or your side?

image
image880×1060 96.8 KB

8

This case it was on our side. Sorry for inconvenience.