# Guest Categories
## Guest Categories
Each guest belongs to a guest category. A lot of MobiCheckin settings ar bound to it.
### Retrieve the list of guest categories
#### JSON
**Request**
```
GET /api/v1/events/{event_id}/guest_categories.json?auth_token=YOUR_API_TOKEN
```
**Response**
```
// 200 OK
[
{
// the first guest category
},
{
// the second guest category
}
]
```
#### XML
**Request**
```
GET /api/v1/events/{event_id}/guest_categories.xml?auth_token=YOUR_API_TOKEN
```
**Response**
```
```
### Get information about a given guest category
If you want to know if the badge is enabled for a guest category, or which check-in points a guest in this guest category can access, use this:
#### JSON
**Request**
```
GET /api/v1/events/{event_id}/guest_categories/{id}.json?auth_token=YOUR_API_TOKEN
```
**Response**
```
// 200 OK
{
"_id": "{id}",
"badge_enabled": true,
"badge_qr_code_enabled": true,
"badge_ecard_in_qr_code_enabled": true,
"confirmation_email_enabled": false,
"rsvp_enabled": false,
"moderated_registrations_enabled": false,
"wufoo_identity_mapping": { },
"wufoo_checkin_point_mapping": { },
"name": "VIPs",
"event_id": "{event_id}",
"updated_at": "2012-11-22T15:07:24Z",
"created_at": "2012-11-22T15:07:24Z",
"guest_category_accesspoints": [
{
"access_once": false,
"accesspoint_id": "{vip_room_id}",
}
]
}
```
#### XML
**Request**
```
GET /api/v1/events/{event_id}/guest_categories/{id}.xml?auth_token=YOUR_API_TOKEN
```
**Response**
```
<_id>{id}
true
true
true
false
false
false
VIPs
{event_id}
2012-11-22T15:07:24Z
2012-11-22T15:07:24Z
false
{vip_room_id}
```
### Create a guest category
#### JSON
**Request**
```
POST /api/v1/events/{event_id}/guest_categories.json?auth_token=YOUR_API_TOKEN
Content-Type: application/json; charset=utf-8
```
```
{
// Fields of the guest category to create (see GET request for a complete list)
}
```
**Response**
```
// 201 Created
{
// Your newly created guest category as a JSON object
}
```
#### XML
**Request**
```
POST /api/v1/{event_id}/guest_category.xml?auth_token=YOUR_API_TOKEN
Content-Type: application/xml; charset=utf-8
```
```
```
**Response**
```
```
### Update a guest category
#### JSON
**Request**
```
PUT /api/v1/events/{event_id}/guest_categories/{id}.json?auth_token=YOUR_API_TOKEN
Content-Type: application/json; charset=utf-8
```
```
{
// Fields of the guest category to update (see GET request for a complete list)
}
```
**Response**
```
// 204 No Content
```
#### XML
**Request**
```
PUT /api/v1/events/{event_id}/guest_categories/{id}.xml?auth_token=YOUR_API_TOKEN
Content-Type: application/xml; charset=utf-8
```
```
```
**Response**
```
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://developers.eventmaker.io/rest-apis/eventmaker-rest-api/guest-categories.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.