> For the complete documentation index, see [llms.txt](https://docs.algomojo.com/algomojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algomojo.com/algomojo/my-api-logs/request-log.md).
# Request Log
The "Request Log" contains a historical record of all API requests made within our system. It includes essential details such as the client ID, timestamp, the name of the API involved, and specific request data associated with each request.
**Search**
You can utilize the search and filtering functionality to explore the logs based on various parameters, enabling you to retrieve specific information.
**CLIENT ID**
The "CLIENT ID" is a unique identifier assigned to the client or user associated with each API request, ensuring proper identification.
**TIMESTAMP**
"TIMESTAMP" records the date and time of each API request, allowing for accurate tracking of the chronological order of events in the log.
**API NAME**
"API NAME" specifies the name of the API involved in each transaction or request, providing context regarding the purpose of the request.
**REQUEST DATA**
"REQUEST DATA" contains specific information and data related to each API request, offering a comprehensive view of the parameters and request details.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.algomojo.com/algomojo/my-api-logs/request-log.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.