Remove Registration
Required plan: EmergingDescription #
You can use the status
property of a Registration
to manage a list of registrants. However, we provide a DELETE
method as a more idiomatic approach if your application doesn’t require the ability to manage multiple registration statuses.
This will update the Registration’s status to be removed
. This will remove it from the list of Registrations associated with the Bookable Event and remove the metadata
associated with the registration.
URL format #
{data_center_url}/v1/bookable_events/{bookable_event_id}/registrations/{registration_id}
Example Request #
DELETE /v1/bookable_events/{bookable_event_id}/registrations/{registration_id} HTTP/1.1
Host: {data_center_url}
Authorization: Bearer {API_KEY}
Content-Type: application/json; charset=utf-8
Example Response #
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{
"bookable_event_id": "83hi8qhfiaif",
"start": "2025-01-03T12:30:00Z",
"end": "2025-01-03T17:00:00Z",
"status": "confirmed",
"registration": {
"capacity": 5,
"registered_count": 0,
"total_count": 1,
"registrations": [
{
"registration_id": "87326",
"status": "removed",
"metadata": null
}
]
}
}
Request parameters #
data_center_url required
The URL for the data center you want to communicate with. Possible choices are:
api-au.cronofy.com
- π¦πΊ Australiaapi-ca.cronofy.com
- π¨π¦ Canadaapi-de.cronofy.com
- π©πͺ Germanyapi-sg.cronofy.com
- πΈπ¬ Singaporeapi-uk.cronofy.com
- π¬π§ United Kingdomapi.cronofy.com
- πΊπΈ United States
Find out more about Cronofy's data centers.
bookable_event_id required #
Your application’s unique identifier for the Bookable Event as a String
.
registration_id required #
The String
that uniquely identifies the registration within the Bookable Event.
Response parameters #
The Bookable Event resource. See Read Bookable Event