> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-few-requests-error.md).

# Troubleshoot Few Requests Error

{% hint style="danger" %}
**At a Glance**: 🛠️ A "Few Requests Error" in Pynt occurs when there are not enough API requests to perform a comprehensive security scan. This guide helps resolve the issue, ensuring sufficient data for accurate security assessments.
{% endhint %}

***

## Error: We identified only X requests. Adding more requests will provide better security test coverage

### What Happened?

Only a few requests were provided as part of the collection, which might limit the coverage of the security tests.

### How to Resolve?

1. **Add More Requests**: Increase the number of requests by adding more API endpoints or more test cases for existing endpoints.
2. **Broaden Test Coverage**: Ensure that your functional tests cover as many API requests and scenarios as possible.

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# 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.pynt.io/documentation/api-security-testing/pynt-scans-troubleshooting/pynt-for-postman-troubleshooting/troubleshoot-few-requests-error.md?ask=<question>&goal=<endgoal>
```

`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.