Using the API log
Navigate to Booking Engine → API Log to inspect recent HTTP conversations between WordPress and booking providers.
Filters
| Filter | Meaning |
|---|---|
| Provider | Narrow rows to one integration slug (e.g. kross). |
| HTTP status | Focus on errors (401, 429, 500, …) vs successes (200). |
Filters apply via drop-downs at the top of the screen (they use URL parameters internally).
Columns explained
| Column | Purpose |
|---|---|
| Time | When the request finished on WordPress. |
| Provider | Integration slug owning the request. |
| Method | HTTP verb (GET, POST, …). |
| Endpoint | Relative path or logical endpoint label recorded by logger. |
| Status | HTTP status code returned (when available). |
| Duration | Round-trip milliseconds—helps detect timeouts vs slow APIs. |
| Correlation | Trace id tying related retries together—share with vendor support. |
| Message | Short human-readable summary / error excerpt. |
Up to 200 newest rows display—plan exports/screenshots early if you rotate logs frequently.
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.