Articles in this section

See more

B-Aggregate: Reporting - Errors

  • Updated

Table of Contents:

Overview

The Errors section provides visibility into API level communication issues between your system and Bakuun.

This page allows Aggregate Demand Partners to monitor booking retrieval failures, authentication issues, and unexpected responses returned by the Channel Manager.

Regular monitoring helps ensure stable connectivity and uninterrupted booking flow.

How to Access

To access this section:

  1. Navigate to Reporting

  2. Click Errors

You will be redirected to the Error Management dashboard.

Error Dashboard

The dashboard displays a list of integration errors with key information for quick review.

Each record includes:

  • Request Time - When the API request was received

  • Channel ID / Channel Name - The connected integration

  • Property - The affected property

  • Type - The API action, for example Bookings

  • Status - Indicates whether the alert has been reviewed

You may filter results by:

  • Date

  • Type - (ARI/Booking)

  • Status - (Acknowledged/Not Acknowledged)

You can mark an error as reviewed by clicking Acknowledge.

Note: Acknowledging an error does not resolve it. It only updates the alert status

Viewing Error Details

To view full technical details:

  1. Locate the error in the list

  2. Click the eye icon on the right

This opens the Error Detail page.

 

Error Detail Page

The Error Detail page provides a complete breakdown of the failed request.

 

Header Information

At the top of the page, you will see:

  • Request Time

  • Channel ID

  • Channel Name

  • Property

  • Alert Status

This confirms which integration and property the error relates to.

Error Summary

The left panel shows:

  • Internal reference

  • API action, for example getBooking

  • Error code, such as 400 ERR or 413 ERR

  • Timestamp of the failed request

Parameters Section

This section provides technical details required for troubleshooting:

  • Response Code - HTTP status returned

  • Response Message - Description of the issue

  • Tracking ID - Unique identifier for the API request

  • Hotel ID / Booking ID - Related identifiers

  • Endpoint - The API URL that was called

Example: 413 ERR - Invalid response from CHM

This indicates that the Channel Manager returned an unexpected or malformed response.

Response Body

The Response Body displays the raw JSON returned by the Channel Manager.

This section is mainly used by technical teams for debugging formatting, authentication, or schema related issues.

Non technical users do not need to interpret the raw JSON.

How to Read Errors if You Are Not Technical

If you are not part of a technical team, focus on:

  • Response Message - Short explanation of the issue

  • Response Code - Indicates whether the request failed

  • Tracking ID - Reference number to share with support

Common examples:

  • “Invalid response from CHM” → Issue likely on the Channel Manager side

  • Authentication error → Credentials may need to be updated

  • Repeated booking errors → Escalate to your technical team

If unsure, share the Tracking ID and timestamp with Bakuun Support for assistance.

Related articles