---
title: "FAQ, MCP & limits"
section: "API Requests"
description: "Answers to common questions about SmartestQA API Requests: Postman comparison, internal APIs, environments, tokens, methods, load tests; MCP; limits."
url: https://docs.smartestqa.ai/en/api-requests-faq.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "api requests faq postman internal api environment token methods patch soap graphql share projects mcp smartest_api_library limits"
---
# API Requests: FAQ, MCP & limits

Answers to common questions about API Requests, how AI assistants work with the API library, and its limits.

## In short

**On this page you can**

- Find quick answers about internal APIs, environments, tokens and methods.
- Let an AI assistant build the API library without handling secrets.
- Check the limits and timeouts of requests.

**How to use it**

1. Filter the questions by your role with the chips.
2. Open a question; follow its link for the full procedure.
3. For AI work, connect an assistant and try the example prompts.
4. Keep the limits table in mind when you design API steps.

## Questions and answers

### Q: Our API is only reachable inside our network. Can we test it?

Yes, in runs on [an agent](https://docs.smartestqa.ai/en/agent-pool-agents.html) or self-hosted runner inside the network. **Send** on the API Requests page and Swagger URL imports go out from the SmartestQA server and cannot reach it; import the spec as a file and check requests with a [Dry Run](https://docs.smartestqa.ai/en/automate-dry-run.html) on the agent. See [Where connections are opened from](https://docs.smartestqa.ai/en/data-source-in-tests.html#where-it-connects).

_Audience: customer, admin_

### Q: How do I call the TEST API in TEST runs and the DEV API in DEV runs?

Start the URL with a key: `{{ds:apiBase}}/orders`. Create `apiBase` and `apiBase_TEST` (and `apiBase_PRP` if needed). Runs pick the variant for their environment; Send uses the default. See [Environment-specific keys](https://docs.smartestqa.ai/en/data-source-variables.html#environments).

_Audience: customer_

### Q: Where do I put the API token?

In an [encrypted key](https://docs.smartestqa.ai/en/data-source-secrets.html#encrypt), for example `apiToken`, and in the request as [**Bearer Token**](https://docs.smartestqa.ai/en/api-requests-editor.html#authorization) `{{ds:apiToken}}`. If the token comes from a login call in the same test, extract it there and use `{{tc:accessToken}}`. See [Authorization in runs](https://docs.smartestqa.ai/en/api-requests-in-tests.html#auth-in-runs).

_Audience: customer_

### Q: Can I use Basic Auth in tests?

Not through [**Basic Auth**](https://docs.smartestqa.ai/en/api-requests-editor.html#authorization): a run applies only [**Bearer Token**](https://docs.smartestqa.ai/en/api-requests-editor.html#authorization). Add the header `Authorization: Basic {{ds:apiBasicAuth}}` instead, with the Base64 of `user:password` in an [encrypted key](https://docs.smartestqa.ai/en/data-source-secrets.html#encrypt).

_Audience: customer_

### Q: I fixed a request in the library. Do my tests use the fix?

No. Each step keeps its own copy. Edit the step’s request, or add the request again. See [Each step keeps its own copy](https://docs.smartestqa.ai/en/api-requests-in-tests.html#copy).

_Audience: customer_

### Q: Which HTTP methods work?

You can save GET, POST, PUT, DELETE, PATCH, HEAD and OPTIONS. Runs send GET, POST, PUT, PATCH and DELETE. **Send** on this page sends POST, PUT and DELETE as such and everything else as GET.

_Audience: customer_

### Q: Do we still need Postman?

For exploring an API, Postman remains handy. For automated checks, import the collection once and use the requests as steps next to UI steps, with shared test data, environments and reports. See [Import a Postman collection](https://docs.smartestqa.ai/en/api-requests-library.html#import-postman).

_Audience: customer_

### Q: Can I test SOAP or XML APIs?

You can store and send XML bodies from this page. In a run, request bodies are sent as JSON, so check an XML request with a [Dry Run](https://docs.smartestqa.ai/en/automate-dry-run.html) before you rely on it. See [Bodies in runs](https://docs.smartestqa.ai/en/api-requests-in-tests.html#body-in-runs).

_Audience: customer_

### Q: Can two projects share the API library?

No. The library belongs to one project. Export from your source (Postman, Swagger) and import it into each project.

_Audience: customer, admin_

### Q: Who can delete requests and folders?

Every project member can delete a single request or an empty folder or collection. A folder or collection with content needs an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html). Steps made from deleted requests keep working.

_Audience: admin_

### Q: Are tokens in saved requests visible to others?

Yes. Tokens and Basic passwords are stored encrypted, but everyone who opens the request sees them in the **Authorization** fields. Use `{{ds:…}}` references to encrypted keys. See [Where secrets belong](https://docs.smartestqa.ai/en/data-source-secrets.html#where-secrets-belong).

_Audience: admin_

## For AI assistants (MCP)

An assistant connected through the SmartestQA MCP server uses `smartest_api_library` to add a request to the library or change one by id: name, url, method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS), headers, queryParams, body, formData, authType, token, username, password, and an optional library folder. Tokens and passwords must be `{{ds:key}}` or `{{tc:…}}` references; a literal secret is refused and nothing is saved. Scenarios then copy a library request into an [API step](https://docs.smartestqa.ai/en/automate-steps-api.html). Connect an assistant from **Device Farm** › **Test Agents** › [**Connect to Claude**](https://docs.smartestqa.ai/en/mcp-connect.html#claude-desktop); more in [Discover › MCP](https://docs.smartestqa.ai/en/discover-faq.html#mcp).

Example prompts

```text
Read our OpenAPI file at ./api/openapi.yaml and add the order endpoints to the API library of project "Web Shop", folder Orders. Use {{ds:apiBase}} as the host and {{ds:apiToken}} as Bearer token.

Write a scenario that creates an order through the API, opens it in the web app and checks the total.

Add a GET request "Health check" to the API library of project "Web Shop": {{ds:apiBase}}/health, no authorization.
```

## Limits

| Item | Limit |
| --- | --- |
| URL | 2,048 characters |
| Basic Auth user name / password | 255 / 128 characters |
| Send and run time limit per request | 30 seconds |
| Methods in runs | GET, POST, PUT, PATCH, DELETE |
| Methods sent as such by Send | POST, PUT, DELETE (others as GET) |
| Authorization applied in runs | Bearer Token |
| Import formats | Postman collection JSON; Swagger / OpenAPI JSON or YAML (file) or JSON (URL); curl |
| Sharing between projects | Not available |
