HTTP Connector Logs
Item DI records detailed logs for all HTTP-based API activity across connectors, flows, MCP servers, and authentication flows. These logs allow developers to inspect request and response details and verify variable injection, data mapping, and API behavior.
View Logs
There are two ways to access the logs:
- Navigate to Integrations → HTTP Logs to view all entries.
- Click View Logs in a specific connector to filter by integration.
Log Filters
Use the filters at the top of the log page to narrow down entries:
| Filter | Description |
|---|---|
| Day | Filter logs by a specific date |
| Connector | Select the integration used (e.g., Shopify, OMS) |
| Operations | Choose a specific operation or feature |
| Sources | Filter by request source (Flow, Connector, MCP, Auth, API) |
| Sort By | Sort logs by creation time or usage time |
| Reset | Clear all applied filters |
View Log Details
Each log entry contains four sections:
| Section | Description |
|---|---|
| Basic Information | Metadata about the request (source, time, connector, etc.) |
| Variables | Runtime parameters injected into the request (e.g., query, headers, body) |
| HTTP Client Config | The request template as configured in Item DI |
| HTTP Request & Response | Actual request sent and response received, with headers and body |
Debugging
Refer to the following section to diagnose API request failures or unexpected behaviors based on the Log Detail view in Item DI.
| Section | Description |
|---|---|
| Variables | Shows all dynamic values injected at runtime, including query params, path variables, headers, and body fields. These values come from schema definitions, flow input, or connector-level configuration. |
| HTTP Client Config | Displays the request template defined in the integration setup. Includes the templated URL, method, body structure, output processing path, and output type (raw, path, or fixed). |
| HTTP Request | Shows the final request sent to the third-party API, with resolved URL, method, headers, and fully substituted body payload. |
| HTTP Response | Displays the full API response, including status code, response time, headers, and the returned body. Used to verify success or inspect error details. |
Source Types
The Source field in the log tells you which DI component initiated the request:
Flow: Triggered by a connector node inside a workflowConnector: Manually triggered by a merchant-level connectorMCP: Triggered from an MCP-compatible serverAuth: Triggered by an authentication flow (e.g., OAuth handshake)API: Triggered from an external system via Item DI's open API interface