## View API log entries in the Developer Tab
API Logs enable you to view your API transaction history and debug API errors with no setup required. When a API request is sent Circle stores it along with its associated response. On the API logs page, you can view these API logs for up to seven days later and filter them to find the specific request you are looking for. To access the logs, go to Circle Sandbox or Circle Account and click on Developer Tab -> Logs.
## API Log Data Elements
For each API request and response Circle will store the following information.
|HTTP Status||HTTP Status code for each request such as 200 or 400.|
|Path||The path excludes the base URL.|
|Request ID||The `|
|User Agent||The User-Agent field in the request header. It is common that the HTTP library used will provide this field by default.|
|Idempotency||Idempotency Key sent in the request body. This is only found in POST requests.|
|Origin||Includes the protocol (HTTP/HTTPS), the domain or IP address, and the port number if applicable.|
|Time||Timestamp of when the request was received.|
|Request Body||The full request body.|
|Response Body||The full response body.|
## API Log Filtering
To filter your search, use the search fields and popup menus at the top of the Circle Sandbox or Circle Account page.
|Search||Filter by request ID, resource ID, or idempotency key ID.|
|Date Range||Filter results by date range.|
|Status||Filter results by `|
|Method||Filter results by HTTP Method. Supports `|
|Path||Filter results by the URL path such as `|
## Data Redaction
Due to the sensitivity of data provided to Circle like financial payment methods and PII data, some values will be redacted from the request and response payloads. Values that are redacted are replaced with the value `