The API Keys section provides TPS users with the credentials needed to authenticate API connections between your system and Bakuun. These keys enable secure access for specific functions such as mapping, ARI updates, and booking retrieval.
Each key is tied to a particular purpose and comes with a creation date, usage tracking, and the option to regenerate when needed.
Note: Keys are sensitive and should only be used by authorized technical users or your channel manager.
API Keys → Mapping Keys
This section displays the credentials used to authenticate API calls for mapping configuration. These keys allow your system to securely send or receive mapping data between your platform and Bakuun.
Table Reference - API Keys → Mapping Keys
| Field | Description |
| Identifies the purpose of the key → either Read (for pulling mapping data from Bakuun) or Post (for pushing mapping data into Bakuun). |
| The actual API key used for authentication. For security, keys are partially masked by default. |
| Shows the most recent timestamp when the key was used. If unused, a dash (–) is shown. |
| The date the key was first generated. |
| Clicking this regenerates the key, invalidating the old one. Use this if a key needs to be rotated. |
| Clicking this will unmask and show the full API key. Make sure to handle keys securely when revealed. |
Note: These keys are used exclusively for mapping configuration. Ensure they are only shared with authorized technical users.
API Keys → ARI Keys
These keys are used to authenticate API calls related to Availability, Rates, and Inventory (ARI). They allow your system to securely push or pull ARI updates from Bakuun.
Table Reference - API Keys → ARI Keys
| Field | Description |
| Identifies the type of ARI key: Read (pull ARI data) or Post (send ARI updates). |
| The authentication string used in API requests. Keys are hidden by default for security. |
| Shows when the key was most recently used. Displays a dash (–) if never triggered. |
| The date the key was first generated. |
| Clicking this regenerates the key, invalidating the old one. Use this if a key needs to be rotated. |
| Clicking this will unmask and show the full API key. Make sure to handle keys securely when revealed. |
Note: Use ARI keys for any automation involving rate, availability, and inventory updates between your system and Bakuun.
API Keys → Booking Keys
These keys are used to authenticate API calls related to booking data. They allow your system to fetch or send booking-related information such as reservations, modifications, or cancellations.
Table Reference - API Keys → Booking Keys
| Field | Description |
| Indicates the key type: Read (to retrieve booking data) or Post (to send booking actions like cancellations or modifications). |
| The secure authentication string used in booking-related API requests. Keys are hidden by default. |
| Displays the last date/time the key was used. A dash (–) means it hasn’t been used yet. |
| The date the key was first generated. |
| Clicking this regenerates the key, invalidating the old one. Use this if a key needs to be rotated. |
| Clicking this will unmask and show the full API key. Make sure to handle keys securely when revealed. |
Note: These keys are essential for syncing your system’s booking records with Bakuun’s platform in real time.