Skip to main content

Operate: Logs - API Logs (LB 2.0)

Marija Golubovic avatar
Written by Marija Golubovic
Updated this week

Overview

The API Logs module provides a centralized view of API requests and responses across core integrations. It replaces the legacy POS Errors screen and exposes technical log data directly within the Admin dashboard, enabling faster investigation of order and integration issues without Engineering involvement.

API Logs are designed for CX, Onboarding, and technical teams who need visibility into what happened to an order at each integration layer.


Accessing API Logs

API Logs are available from the Admin dashboard.

  1. Select Operate

  2. Select Logs

  3. Select API logs

Here we can see detailed records of API requests and responses, which help us track usage, monitor performance, and debug issues. The page includes controls that allow filtering and sorting logs, including:

  • Order ID

  • External Order ID

  • Service Type

  • Date (By default, logs from the last 7 days are visible)

  • Sort By (Created Time)

POS logs

The POS Logs show POS Log ID, Order ID, Date/Time, Type, and Status

Order Providers

Under order providers, we can view logs: External Order ID, Order ID, Date/time, Provider, and Status.

The log details

Delivery

Delivery logs show External ID, Order ID, Date/Time of the order, Provider, and Status.

The delivery log details

Payments

Payment logs show External Order ID, Order ID, Date/Time, Gateway, Transacton and Status.

Payment log details


Log Details

The POS tabs present POS Log ID, Order ID, Date/ Time, POS type, and Status. Additionally, we can view Log details by selecting the More button> Details

The pop-up window will show Log summary, as well as the raw JSON file of the log, which can be used for easier troubleshooting. Additionally, we can download and copy the log summary and the Raw JSON file.

Log Summary contains: log date and time, external order ID (if any), external Status ID (if any), integration type, order ID, POS log ID, Service Name, Status, the length (time) and timestamp of the log.

IMPORTANT NOTE: API Logs automatically redacts sensitive information. Passwords, payment details (for example, credit card numbers), and PII are not exposed in the UI and cannot be accidentally copied or downloaded..

Share logs when escalation is needed (Copy/Download)

When a case requires escalation to Engineering or a third-party partner (for example, DoorDash support), API Logs provides one-click reporting:

  • Use Copy to copy the full payload for a log entry.

  • Use Download to export the payload as a file.

Paste or attach the payload directly in the ticket or partner email to provide a complete technical context and reduce follow-up questions.

Did this answer your question?