How to Verify Credentials in Your Postman Collection
Last updated: November 20, 2026
Your Postman collection tells Astra which endpoints to test, and the credentials in it decide how far testing gets. If a token has expired or an environment variable holds the wrong value, Astra can't test your API properly.
Credential verification checks this before you scan. An AI agent reads your collection, its environment file and the target's authentication, sends requests to your endpoints with the credentials it finds, and reports which endpoints accept them.
Availability
Credential verification is available for API targets and for the API Scanning page of web app targets, on plans that include AI credential verification. It supports Postman collections only. Hoppscotch collections and HAR files aren't checked.
What gets checked
The agent looks for credentials in three places:
Collection. The authorization set on the Postman collection.
Environment. The variables in the environment file you uploaded with the collection.
Target. The authentication saved on the target in Astra. This applies to API targets only.
The check is read-only. It sends only non-destructive requests, so it doesn't create, change or delete data on your API, and credential values never appear in the report.
Before you start
A Postman collection is uploaded to the target. Upload the environment file too if your collection uses variables such as
{{token}}.The target has a URL to test: the API base URL of the target. For a web app target, it is the API base URL on the API Scanning page.
Your API is reachable from Astra. If you limit inbound traffic by IP address, allow Astra's scanner IPs. Read more in đź“„ Astra IP Ranges.
Run the check
Open the Targets page. For a target that is still being set up, click Setup on its row and open API definitions. For an active API target, click the settings icon on its row and open Definition Files. For a web app target, open API Scanning.
Open the Postman tab and upload the collection and its environment file, if you haven't already.
Click Verify with AI under the collection.
Wait for Verifying your credentials… to finish. You can close the sheet while it runs. The result appears under the collection.
If the button is unavailable, hover over it. Astra asks you to add a URL to the target first.

The Definition Files page shows the verification result under the uploaded collection.
Read the result
Result | What it means | What to do |
|---|---|---|
Check that these credentials work | The credentials haven't been checked yet. | Click Verify with AI. |
Verifying your credentials… | The check is running. | Wait for the result. While it runs, you can't replace or remove the collection or the environment file. |
Your credentials work | Testing can use these credentials. | Run the check again whenever you change them. |
Some endpoints rejected your credentials | Some endpoints didn't accept them. | Open the report, fix the collection or environment file, and click Verify again. |
Your credentials didn't work | No endpoint accepted them. | Update the credentials in the collection or environment file, and click Verify again. |
We couldn't verify your credentials | Nothing in the check reached your API. | Fix the cause, for example the URL or missing variables, and click Verify again. |
Verify your credentials again | The last result no longer applies because you changed the credentials, the collection or the environment file. Astra shows which change and when. | Click Verify again. |
Under the result, Astra shows when the check ran. Click View report for the details.
Open the report
View report opens the Postman Collection Verification Report. It lists every tested endpoint with its method, whether it needs authentication, where the credentials came from, and a status:
Status | What it means |
|---|---|
Working | The endpoint accepted the credentials, or it doesn't need authentication. |
Needs review | Astra couldn't decide, often because a variable has no value. |
Failed | The endpoint rejected the credentials. |
Filter the list by Failed, Needs review or Working. For failed endpoints, the report shows a Next step.

The verification report lists each tested endpoint and whether the credentials worked.
Troubleshooting
If the result is not Your credentials work, check the common causes below. After you fix one, click Verify again.
Cause | What you'll notice | How to fix it |
|---|---|---|
Expired token | Endpoints that worked before now fail. | Create a fresh token and update it in the collection, the environment file or the target's authentication. |
Empty or unresolved variables | Endpoints are marked Needs review or aren't tested. | Upload the environment file, and make sure every variable the collection uses has a value and a matching name. |
Wrong base URL | Most or all endpoints fail or return not found. | Check the API base URL saved on the target. |
Blocked IP addresses | Requests time out or are refused. | Allow Astra's scanner IPs. |
Role or scope is too narrow | Some endpoints sign in but are denied access. | Use credentials whose role or scopes can reach every endpoint you want tested. |
Best practices
Verify after every change. Run the check again when you upload a new collection, replace an environment file or change the target's credentials.
Verify against a stable environment. Use a staging environment that matches production, so the credentials you verify are the ones the scan uses.
Verify before you import. An endpoint import waits until credential verification finishes. Verify first, and then import so the next scan covers your endpoints.
Read more in đź“„ How to verify API credentials in a Postman collection and đź“„ How to import your API endpoints.