Developer logs in the Kustom Portal are retained for 14 days. Use them to:
Investigate technical issues related to orders or your integration.
Review the request and response of a specific API call.
Export logs to share with your developer, platform partner or Kustom support.
Our technical documentation is available at docs.kustom.co.
Where to find the Developer logs
Open the Kustom Portal and sign in.
Select Developers in the menu on the left, then select Developer logs.
The page opens with the last 14 days selected. The date range is shown as concrete dates so you always know which period you are looking at. Selecting a single day includes the full 24 hours of that day.
[Screenshot: Developer logs page with filter bar]
Filtering and searching
Use the filters above the table to narrow down the logs:
Date range: The period to show logs for, up to 14 days back.
Type: Incoming or Outgoing (see Reading the Developer logs).
Service: The Kustom service that produced the log, for example Checkout or Order Manager. Useful when you only want to see order management calls or only checkout calls.
Status: HTTP status code of the response.
Event: The underlying Kustom event, for example ORDER.
Filter options are listed alphabetically with All at the top. Press the X to the right of the filters to reset them.
To search, click the search icon in the table toolbar. The search matches a complete Reference ID or Correlation ID. Partial IDs will not return results, so paste the full ID.
The table shows 100 rows per page. Timestamps are shown with millisecond precision so you can tell apart events that happened within the same second.
Reading the Developer logs
Each row in the table represents one API call:
Request timestamp: When Kustom received or sent the request, shown in your local time.
Action: Human-readable Kustom API action triggered by the request, for example CREATE_ORDER or UPDATE_ORDER.
Service: The Kustom service that handled the call.
Status: HTTP status code returned in the response. See HTTP status codes below.
Method: HTTP request method (GET, POST, PATCH, etc).
Reference ID: The Kustom order ID. Click it to see all logs related to that order.
Event: The underlying Kustom event.
Type: Direction of the call.
Incoming: Your system to Kustom.
Outgoing: Kustom to your system, for example callbacks and push notifications.
If your store is connected to a partner, a Partner column shows which partner each event belongs to. Use the columns icon in the toolbar to show or hide columns.
Log details
Click a row to open the log details. At the top you see the method, status code and endpoint path, followed by the metadata for the call:
reference-id: The order ID.
correlation-id: Ties together all calls that belong to the same request flow. Include this when contacting support.
producing-system: The Kustom service that produced the log.
log-id: Unique ID for this specific log entry.
Switch between the Request and Response tabs to see the headers, parameters and body of each. Hover over the body and click the copy icon to copy it. The copied content pastes as indented JSON, exactly as shown on screen.
[Screenshot: Log details drawer with Request tab and body]
Exporting logs
You can export logs to CSV to share them or analyse them outside the portal.
Tick the checkbox on each row you want to export, or tick the checkbox in the table header to select all rows on the current page.
Click the download icon in the table toolbar. The tooltip shows how many logs will be exported.
The CSV contains the complete request and response bodies for each log, not only the columns visible in the table.
[Screenshot: Rows selected with export tooltip]
You can also share a direct link to a log. The link opens the correct view for whoever clicks it, whether they are a user on your store or a member of Kustom support.
HTTP status codes
HTTP response status codes are organised into categories according to their first digit:
2xx (Success): The request was successfully received, understood and processed.
3xx (Redirection): The request needs additional actions to be completed, typically involving a redirection, for example when a customer selects an unsupported shipping country.
4xx (Client errors): The request failed because of an error on the calling side, such as invalid data or a missing permission.
5xx (Server errors): Kustom failed to process the request due to an error on our side.
See more detailed information in Kustom docs.