Skip to main content

Using Tools & Logs

Navigate to Booking Engine → Tools & Logs to inspect recent HTTP conversations between WordPress and booking providers.

Tools & Logs admin screen


Filters

FilterMeaning
ProviderNarrow rows to one integration slug (e.g. kross).
HTTP statusFocus on errors (401, 429, 500, …) vs successes (200).

Filters apply via drop-downs at the top of the screen (they use URL parameters internally).


Database table

Rows are stored in the custom table {prefix}bec_api_log (created on upgrade via plugin migrations tracked by the bec_db_version option). Typical columns:

ColumnPurpose
idAutoincrement primary key.
created_atRequest completion time (server time).
provider_slugIntegration key (e.g. kross).
http_methodVerb (GET, POST, …).
endpointPath or logical label (stored as text).
status_codeHTTP status when available.
duration_msRound-trip duration.
error_categoryNormalised error bucket when classified (nullable).
messageShort summary / excerpt (nullable).
unit_idRelated bec_unit post ID when the logger tied the call to a unit (nullable).
correlation_idX-BEC-Correlation-Id header value for bundled retries.

Columns explained

ColumnPurpose
TimeWhen the request finished on WordPress.
ProviderIntegration slug owning the request.
MethodHTTP verb (GET, POST, …).
EndpointRelative path or logical endpoint label recorded by logger.
StatusHTTP status code returned (when available).
DurationRound-trip milliseconds—helps detect timeouts vs slow APIs.
CorrelationTrace id tying related retries together—share with vendor support.
MessageShort human-readable summary / error excerpt.

Up to 200 newest rows display—plan exports/screenshots early if you rotate logs frequently. The admin UI mirrors the most useful subset of the database columns described above.


Auth rows

Sensitive auth/token exchanges may be omitted unless developers explicitly enable logging via bec_log_auth_requests filter—don’t panic if login succeeds yet auth rows stay hidden.