1. Docs
  2. Resources
  3. API Requests
  4. Troubleshooting

Troubleshooting

Find the message or symptom you see. Each entry says why it happens, what to check and how to fix it.

8 min read Updated CustomersAdmins

In short

On this page you can

  • Look up an API Requests message and see why it appears.
  • Fix Send errors: timeout, unknown host, refused connection.
  • Fix imports from Postman, Swagger / OpenAPI and curl.
  • Fix API steps that behave differently in a run.

How to use it

  1. Copy the first words of the message you see.
  2. Find the entry with the same words below.
  3. Work through Check, then apply Fix.
  4. Still stuck: send the message and the run link to info@smartestqa.ai.

The API tree#

“API requests could not be loaded.”Tree
Why
The tree could not be read: session expired, network problem, or no project selected (“Please select a project”).
Fix
Click Retry. If it stays, select the project again or log in again.
“Request could not be created.” / “Folder could not be created.” / “Collection could not be created.”Tree
Fix
Refresh the page and try again. Select an existing collection or folder first; a parent deleted in another tab cannot take new items.
“Error during update.”Tree
Why
A rename or a drag-and-drop move was rejected.
Fix
Refresh and try again. Collections and the top folder cannot be moved, and a folder cannot go into its own sub folder. See Move.
“Folder … could not be deleted.” / “Collection … could not be deleted.” / “Request … could not be deleted.”Tree
Why
A folder or collection that still has content can only be deleted by an Admin. For a request, or “Server error during deletion.”, the server rejected the delete.
Fix
Ask an Admin, or empty the folder first. Steps made from the requests keep working. See Delete.

Imports#

“Invalid Postman collection format” / “Please select a valid JSON file”Postman
Why
The file is not JSON, or it is not a collection export (it lacks info and item). Postman environment files and data dumps look similar but are not collections.
Fix
In Postman, export the collection itself and import that file. “Please select a file” means none was chosen. See Import a Postman collection.
“Import error: …”Postman
Why
The server could not import the collection; the text after the colon is its reason.
Fix
Correct what the reason names, or import a smaller collection. When n/total shows fewer requests than expected, compare the collection and the tree and add the missing ones by hand.
“This looks like a Swagger UI page, not the JSON spec…” / “URL returned HTML, not JSON…”Swagger
Why
The address is the documentation page, not the specification.
Fix
Use the JSON endpoint, usually /v3/api-docs, /v2/api-docs, /swagger.json or /openapi.json. In Swagger UI it is the link under the API title.
“Failed to fetch Swagger spec: HTTP …” / “Swagger URL returned an empty body.”Swagger
Why
The SmartestQA server downloaded the address and got an error status (for example 401 or 404) or nothing.
Check
The URL opens without a login, and it is reachable from the internet.
Fix
Download the spec yourself and use File Upload (JSON or YAML).
“URL is required. Please enter a request URL.” / “Invalid URL. Please enter the address starting with http:// or https://.” / “Please provide a file or URL.”Swagger
Fix
Enter a full address beginning with http:// or https:// on the URL tab, or choose a file on File Upload.
“No URL found in the curl command.” / “Empty curl command.” / “Failed to parse the curl command.”curl
Why
The text is empty, has no address, or has unbalanced quotes.
Fix
Copy the command again (“Copy as cURL (bash)” in the browser) and paste it whole. In Automate, “Failed to create the API request.” means the parsed request could not be saved; try again.

Editing and Save#

“URL is required. Please enter a request URL.”Save
Fix
Enter a URL. It may be relative or contain references; see Save.
“Invalid URL. Please enter the address starting with http:// or https://.” when savingSave
Why
The URL uses a Data Source key whose value is not a full address.
Fix
Open the key in Variables and give it a value that starts with http:// or https://, for example https://test.shop.example.com/api.
“An error occurred while saving. Please try again later.”Save
Fix
Refresh, then save again. A Basic Auth password longer than 128 characters or a URL longer than 2,048 characters cannot be stored.
“Authorization could not be saved. Please try again.” / “No folder or collection selected.”Authorization
Fix
Select the collection or folder in the tree, set the authorization and click Save Auth again. See Inherited authorization.
“No authorization set on parent collection/folder. Set it there first.”Authorization
Fix
Set Bearer or Basic on the collection or a folder above the request and click Save Auth. For requests you will use in tests, set Bearer Token on the request instead; see Authorization in runs.
A header or parameter row disappeared after savingEditing
Why
Rows switched off with Enable row are not saved.
Fix
Switch the row on before saving, or keep a variant of the request with Duplicate.

Send#

“You can save this address and use it in a test case; global parameters are resolved during the run. But to send it directly from here, the URL must start with http:// or https://.”Send
Why
After Data Source keys are filled in, the URL is still not a full address: it is relative (/api/orders) or starts with a run-time reference such as {{tc:baseUrl}}.
Fix
Start the URL with a Data Source key that holds a full address, {{ds:apiBase}}/orders, or try it with the step’s Send in Automate, which asks for test values. See What Send sends.
“The request timed out (30s). The target did not respond.”Send
Why
No answer within 30 seconds. Often a firewall that silently drops traffic from the SmartestQA server, or a slow endpoint.
Fix
Check that the API is reachable from the internet, then click Retry. For internal APIs, test with a Dry Run on an agent.
“Host not found. Please check the URL.”Send
Why
The host name does not resolve from the SmartestQA server: a typo, or an internal name such as api.intranet or localhost.
Fix
Correct the host. Internal hosts can only be reached by a run on an agent inside your network (Do you need an agent?).
“Connection refused. The target is not reachable.”Send
Why
The host exists but nothing accepts connections on that port, or a firewall rejects SmartestQA.
Fix
Check the port and protocol (http vs https) and the firewall. Then Retry.
“The request could not be completed. Please try again.” / “An error occurred while sending the request. Please try again later.”Send
Why
Another network or protocol error, for example a TLS certificate the server does not trust, or an address that is not a valid URL.
Fix
Check the URL, open it in a browser, and click Retry. For self-signed certificates, use a test endpoint with a valid certificate.
PATCH, HEAD or OPTIONS behaves like GET on this pageSend
Why
Send on the API Requests page sends only POST, PUT and DELETE as such; every other method goes out as GET.
Fix
Test PATCH with a Dry Run of an API step: runs send PATCH. HEAD and OPTIONS are not supported in runs either.
My Params rows are not in the requestSend
Why
Send uses only the query string in the URL. Test runs add the Params rows.
Fix
To try them here, write them into the URL: ?page=1&size=20.
The API receives {{tc:…}} or {{ds:apiToken}} as textSend
Why
Send on this page fills only Data Source keys in the URL. Headers, body and token are sent as typed.
Fix
Use the step’s Send in Automate with Test values, or a Dry Run. Encrypted keys are only ever filled in a run.

API steps in runs#

Works with Send, but the run gets 401 UnauthorizedRuns
Why
The step uses Basic Auth or Inherit from parent. A run applies only Bearer Token. A pasted curl with -u or Authorization: Basic becomes Basic Auth too.
Fix
Set Bearer Token on the step’s request, or add an Authorization header with Basic {{ds:apiBasicAuth}}. See Authorization in runs.
“Unsupported HTTP method”Runs
Why
HEAD and OPTIONS can be saved but a run supports only GET, POST, PUT, PATCH and DELETE.
Fix
Change the method of the step’s request, for example to GET, and check the headers you need with an extractor.
I changed the request in API Requests, but the test still sends the old oneRuns
Why
Each step keeps its own copy of the request.
Fix
Edit the request inside the step, or remove the step and add the request again. Keep changing parts in Data Source keys. See Each step keeps its own copy.
“Failed to load API request; step not added.” / “No API requests available”Automate
Why
The request could not be read, for example because it was just deleted in another tab. “No API requests available” means the library of this project is empty; “No results found” means the search matched nothing.
Fix
Close the dialog, refresh the test case and try again, or create the request first in API Requests or with Create from curl.
The run cannot reach the API, but Send can (or the other way round)Runs
Why
Send goes out from the SmartestQA server; a run goes out from the machine that runs the test. See Where connections are opened from.
Fix
Run the test where the API is reachable, typically an agent inside your network, or open the firewall for the runner.
The API step fails with an SSL or certificate error in the runRuns
Why
API steps always verify the server’s certificate. Self-signed or expired certificates fail. The test case continues with the next step.
Fix
Use a test endpoint with a valid certificate from a public certificate authority.
The API rejects the body in a run (XML or plain text)Runs
Why
A run sends the body as JSON. A body that is not JSON is sent as a JSON text in quotes, and form-data rows are not sent.
Fix
Use a JSON body where the API allows it, and check the request in the Dry Run log. See Bodies in runs.
The API returned 500, but the step passedRuns
Why
Any HTTP status counts as a completed call.
Fix
Extract @status in the step and add an assertion such as “equals 201” after it. That part is described in Automate.

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai
© 2026 Selenity Technology · SmartestQAsmartestqa.aiThis page as MarkdownChecked against smarttest-fe predev 2a8c79cc, smarttest-be 633c2a03, smarttest-testsuite (runner)