Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints

Get public facility availability
Create outbound webhook for facility Use this endpoint to create a public inline booking request for a facility with an API key-protected flow.

What happens after a request

The booking request is submitted from your site or widget flow.
The request goes to the facility manager for review in the Rondo dashboard.
The facility manager can approve or reject the request.
You can subscribe to booking lifecycle notifications through the facility webhook endpoints.

Known conflict response

If another request claims the same slot first, Rondo returns 409 with this response body:

{
  "error": "Slot no longer available",
  "code": "SLOT_CONFLICT"
}

Related endpoints