> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/build/api-logs.md).

# API Call Logs

View complete records of all API calls to MaiAgent services, including request content, response results, and performance data

## Overview

API Call Logs provide a complete record of all requests made through the MaiAgent API, including HTTP method, endpoint path, status code, response time, request and response content, and more. This is ideal for developers to debug, monitor performance, and track usage during API integration.

***

## View Logs

In the left menu, click <mark style="color:blue;">Developer</mark> → <mark style="color:blue;">API Call Logs</mark> to view the list of all API request records.

### Record Field Descriptions

| Field             | Description                                                                           |
| ----------------- | ------------------------------------------------------------------------------------- |
| **ID**            | Unique identifier for the request                                                     |
| **Method**        | HTTP method (GET, POST, PUT, DELETE, PATCH), color-coded                              |
| **Endpoint**      | API endpoint path                                                                     |
| **Status Code**   | HTTP response status code, color-coded by type: 2xx (green), 4xx (orange), 5xx (red)  |
| **Duration**      | Request duration, color-coded by speed: <100ms (green), <500ms (orange), >500ms (red) |
| **Request Body**  | Request content preview                                                               |
| **Response Body** | Response content preview                                                              |
| **IP Address**    | Source IP of the request                                                              |
| **Time**          | Request time                                                                          |

***

## Filter and Search

Use the filter bar at the top to quickly find the records you need:

* **Date Range**: Select start and end dates to view records for a specific time period
* **HTTP Method**: Filter by method (GET, POST, PUT, DELETE, PATCH)
* **Status Category**: Filter by response status (2xx Success, 4xx Client Error, 5xx Server Error)
* **Keyword Search**: Enter an endpoint path or other keywords to search

{% hint style="info" %}
When troubleshooting API integration issues, filter by 4xx or 5xx status codes first to quickly locate failed requests.
{% endhint %}

***

## View Request Details

In the record list, click the view icon on the right side of any record to expand the full request and response details, including the complete Request Body and Response Body, for developer debugging.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maiagent.ai/maiagent-user-guide/en/build/api-logs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.