> For the complete documentation index, see [llms.txt](https://developer.siteminder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.siteminder.com/smx-api/additional-resources/reference-tables/service-and-extra-charge.md).

# Service and Extra Charge

Contains ServiceInventoryCode for additional services or charges.

For channels/OTA's under **SiteConnect API**: Use this list as a guide to code your extras/services. You can use additional codes not on the list such as PARKING or your own service identifier codes generated in your system.

For PMSs under **pmsXchange API**: Channels/OTA's will use this list as a guide to code the extras/services or can use their own codes as well. Please request the property or the channel for the full list of extras/services and the codes.

<table><thead><tr><th width="185">Type</th><th width="480">Description</th></tr></thead><tbody><tr><td>EXTRA_PERSON</td><td>Charges related to extra people</td></tr><tr><td>EXTRA_BED</td><td>Extra bed charges</td></tr><tr><td>SURCHARGE</td><td>Surcharges, for example credit card surcharge</td></tr><tr><td>MEAL</td><td>Charges related to the meal</td></tr><tr><td>SERVICE</td><td>General hotel nominated service charges</td></tr><tr><td>TOUR</td><td>Charges for a tour</td></tr><tr><td>EVENT</td><td>Charges for an event</td></tr><tr><td>EXTRA</td><td>Un-categorised extra added to the reservation</td></tr><tr><td>OTHER</td><td>Any additional charge that does not fall under the above categories, where OTHER is specified more information will be provided in the description</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.siteminder.com/smx-api/additional-resources/reference-tables/service-and-extra-charge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.