# Query and investigate request logs

Locate a call, inspect its result and upstream attempts, and download the complete request or response after its body has been archived.

## Prerequisites

Prepare a personal access token and the time range, model, or calling credential information for the investigation. For authentication and query scope, see [Usage and monitoring](../../../../reference/api/genesis/management/index.md).

## Call sequence

1. Query request logs and use time and call information to locate the target record and obtain its log identifier.
2. Query details using that identifier to inspect the call result, body previews, and archive information.
3. To investigate upstream processing, use the same log identifier to query upstream request records and inspect each attempt.
4. If you need a complete body, first confirm in the details that it has been archived. Then download it using a body archive reference belonging to that same log.

## API operations

| Task | API operation | When to use it or what to confirm |
| --- | --- | --- |
| Locate a call | [List request logs](../../../../reference/api/genesis/management/request-logs/list-request-logs.md) | Browse filtered calls and obtain a log identifier. |
| Inspect call details | [Get request log details](../../../../reference/api/genesis/management/request-logs/get-request-log.md) | Inspect the result, body previews, and archive information. |
| Inspect upstream attempts | [List upstream request attempts](../../../../reference/api/genesis/management/request-logs/list-provider-requests.md) | Review each upstream request and its result for this call. |
| Retrieve a complete body | [Download a request or response body](../../../../reference/api/genesis/management/request-logs/download-body.md) | Use after archiving is complete and the corresponding reference is available. |

## Confirm the result

Confirm the target call with [Get request log details](../../../../reference/api/genesis/management/request-logs/get-request-log.md). Check that upstream records belong to that log. After downloading a body, use the size and checksum information in the details to check completeness.

## Limitations and notes

- Queries return only records accessible to the current user.
- A preview is not a complete body. The existence of a log does not mean its body archive is complete.
- The log identifier and body reference used for a download must belong to the same log. Downloads return raw bytes, not a JSON envelope.
- Request and response bodies may contain business data. Confirm access scope before saving or sharing them and avoid exposing sensitive content.

## Next steps

- [Analyze call usage](usage.md)
- [Query model catalogs and runtime status](models-and-status.md)