# Profile List

{% hint style="warning" %}
If the profile you are looking for is not listed please get in touch so we can create for you.
{% endhint %}

## Understanding Profiles

**Profiles are blueprints for credit card handling:** Each Vaultera profile defines how to tokenize or detokenize credit card details for a specific booking engine or data source. It outlines where the card information is located in the booking data and how to replace it with a secure token (during tokenization) or reinsert the real card data (during detokenization).

**Using a profile token when fetching bookings:** When you retrieve bookings via Vaultera, you must specify which profile to use for credit card handling. In your API request, include the profile’s token name (for example, `profile=site_minder` or `profile=booking_com_body`). This tells Vaultera which blueprint to apply, ensuring credit card numbers are properly tokenized (or detokenized) in the returned data.

**Profile List page is informational only:** The list below shows all pre-created profiles and their token names for reference. This page is for informational purposes – it is **not** an interface for direct interaction (editing or selecting profiles). If you need a new profile that isn’t listed, please get in touch with us to have it created.

## Header or Body

Vaultera PCI can provide the token in the header or in the body of the booking. You will need to select the correct profile depending which is your preference.

## Request New Profiles

Please email us if you need a new profile created. We need the full response (XML or Json) examples with one and/or with multiple bookings.

## Created Profiles

We have profiles for these services already created, please use in your request

<table data-header-hidden><thead><tr><th width="176.33333333333331">Company</th><th>Token Name (Header)</th><th>Token Name (Body)</th></tr></thead><tbody><tr><td>Company</td><td>Token Name (Header)</td><td>Token Name (Body)</td></tr><tr><td>My Allocator</td><td></td><td>myallocator</td></tr><tr><td>Siteminder</td><td>site_minder</td><td>site_minder_body</td></tr><tr><td>Vertical Booking</td><td>vertical_booking</td><td></td></tr><tr><td>Wubook</td><td>wubook</td><td>wubook_body</td></tr><tr><td>Booking.com</td><td>booking_com</td><td>booking_com_body</td></tr><tr><td>Expedia</td><td>expedia</td><td>expedia_body</td></tr><tr><td>Hostel World</td><td>hostelworld_xml, hostelworld_json</td><td>hostelworld_xml_body</td></tr><tr><td>Agoda</td><td>agoda</td><td>agoda_body</td></tr><tr><td>Yieldplanet</td><td>yieldplanet</td><td></td></tr><tr><td>Staah</td><td>staah</td><td></td></tr><tr><td>Channex</td><td></td><td>channex, channex_entity</td></tr><tr><td>Ctrip</td><td></td><td>ctrip</td></tr><tr><td>Despegar</td><td></td><td>despegar</td></tr><tr><td>Dorms</td><td></td><td>dorms</td></tr><tr><td>Hotelbeds</td><td>hotelbeds</td><td></td></tr><tr><td>Hotetec</td><td>hotetec</td><td></td></tr><tr><td>Inntopia</td><td>inntopia</td><td></td></tr><tr><td>Nextpax</td><td>nextpax</td><td></td></tr><tr><td>Cubilis</td><td>cubilis</td><td></td></tr></tbody></table>


---

# 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://docs.vaultera.co/profile-list.md?ask=<question>
```

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.