Developer Account Logs

View API log entries in the Web3 Services Console

API logs enable you to view your API transaction history and debug API errors with no setup required. When an API request is sent, Circle stores it along with its associated response.

On the API logs page, you can view logs for up to seven days and filter them to find the specific request you are looking for. Go to your Web3 Services Console to access the logs and click Logs.

API Log Data Elements

For each API request and response Circle will store the following information.

HTTP StatusHTTP status code for each request, such as 200 or 400.
PathThe path of the resource (excludes the base URL).
Request IDThe X-Request-Id field in the request header or returned in the response.
User AgentThe User-Agent field in the request header. Commonly, the HTTP library used will provide this field by default.
IdempotencyIdempotency key that was sent in the request body. This is only found in POST requests.
OriginIncludes the protocol (HTTP/HTTPS), the domain or IP address, and the port number if applicable.
TimeTimestamp of when the request was received.
Request BodyThe full request body.
Response BodyThe full response body.

API Log Filtering

To filter your search, use the search fields and popup menus at the top of the Circle Developer account page.

Filter NameDescription
SearchFilter by request ID, resource ID or idempotency key ID.
Date RangeFilter results by date range.
StatusFilter results by successful and/or failed requests. Succeeded includes all 2## codes and failed includes all 4## and 5## codes.
MethodFilter results by HTTP method. Supports POST, PUT, PATCH, DELETE and GET.
PathFilter results by the URL path, such as /transactions.