Skip to main content
Find an API request, check its result, and investigate failures. API Logs records API requests for your broker. You can review the available request and response data.

Who Can Do This

Only broker admins can open API Logs. Staff accounts do not have access.

Open API Logs

1

Sign In as an Admin

Sign in with a broker admin account.
2

Open API Center

Open API Center under Integrations in the sidebar.
3

View the Logs

Select View Logs on the API Logs card.

Filter the Request Logs

Request Logs filters above a table of live and test API requests

Request Logs Table

Each row shows the timestamp (UTC), HTTP method, endpoint, response status, Mode (Live, Test, or Unknown), source IP address when available, and the View Log action. Filters work together, and a filter change returns the table to page 1.

Open Log Details

API Request Details dialog with request and response data

API Request Details

1

Find the Request

Find the request in the Request Logs table.
2

Select View Log

Select View Log. The API Request Details dialog opens.
The dialog shows the full timestamp and a Request Overview. The overview includes Method, Status Code, Endpoint, Mode, IP Address, and User Agent.
The dialog can also show these sections:
  • Request Body shows captured request data. For GET and DELETE requests, this section can show query parameters instead of a body.
  • A content type badge can appear beside Request Body.
  • A Truncated badge means the logger stored only part of a large request body.
  • Response Body shows a captured JSON response. A non-JSON response can appear as No response body.

Debug a Failed Request

1

Filter to the Request

Filter by the shortest Date Range that contains the request, part of the API path in Search, and the 4xx or 5xx Status class.
2

Open the Log

Select View Log for the matching row.
3

Compare with Your Integration

In API Request Details, compare the Endpoint, Method, Mode, and Status Code with your integration.
4

Review the Bodies

Review Request Body for missing or invalid input. Review Response Body for a safe error message.
5

Fix or Retry

For a 4xx result, correct the request before you retry it. For a 5xx result, retry only after you confirm that a repeated request is safe.
If the 5xx result continues, send support the timestamp, endpoint, method, mode, and status code. Do not send request bodies, response bodies, credentials, tokens, IP addresses, user agents, or client data.

Next Step

Read the API Reference

See authentication, endpoints, and request and response examples.
Last modified on October 4, 2026