# Page Not Found

The URL `files/IqjSr51CvIuu5J7P1lua` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Prerequisites for Running Pynt Scans](https://docs.pynt.io/documentation/api-security-testing/prerequisites-for-running-pynt-scans.md)
- [Injection Tests](https://docs.pynt.io/documentation/api-security-testing/pynt-security-tests-coverage/injection-tests.md)
- [Manage API Source Gaps](https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps.md)
- [Pynt Security Tests Coverage](https://docs.pynt.io/documentation/api-security-testing/pynt-security-tests-coverage.md)
- [GraphQL Introspection Vulnerability](https://docs.pynt.io/documentation/api-security-testing/pynt-security-tests-coverage/graphql-introspection-vulnerability.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.pynt.io/documentation/api-security-testing/prerequisites-for-running-pynt-scans.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.pynt.io/documentation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.pynt.io/documentation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/documentation/api-security-testing/prerequisites-for-running-pynt-scans.md`).

You may also use `Accept: text/markdown` header for content negotiation.