Troubleshooting
Short answers to the issues that come up most often. If something here does not match what you see, reach out.
My Authorization header disappears after a redirect
By design. When a request is redirected to a different host, Ironcall strips sensitive headers (Authorization, Cookie, and similar) before following the redirect, so credentials are never sent to an unexpected origin. Point the request directly at the final URL, or add the header again for that host.
A self-signed certificate is rejected
Ironcall validates certificates against the system trust store. For a development server with a self-signed certificate, toggle SSL verify off in the request settings panel. Do this only on local or trusted networks. To trust a private CA or present a client certificate (mTLS) instead, add an entry in the Certificates manager (open it from the footer).
How do I call a GraphQL API?
There is no dedicated GraphQL mode. Send a POST with a JSON body containing query and, if needed, variables:
{ "query": "{ user(id: 1) { name } }", "variables": {} }
Does Ironcall support OAuth 2.0?
Yes. Select OAuth 2.0 in the Auth tab, alongside Bearer, Basic, and API Key. Both Authorization Code (with PKCE) and Client Credentials grants are supported. See Authentication.
My imported Postman collection has no tests or scripts
Pre-request and test scripts are not imported from Postman or Insomnia, because Ironcall uses a different scripting model. Requests, folders, headers, parameters, bodies, and auth are imported. See Import & Export.
My script reads ic.response.time and gets undefined
The response duration property is ic.response.duration_ms. See Scripts.
My script was terminated
Scripts run with a 64 MiB memory limit and a 2-second wall-clock budget. A script that exceeds either is stopped and the request is marked as failed. Move heavy work out of the script, or split it across requests.
A large response looks truncated
Response bodies are capped at 100 MiB. Anything beyond the cap is dropped to avoid exhausting memory.
ironcall run exits with code 2
Exit code 2 means no requests were found at the path you passed. Check that the path points to a collection file or an exported collection folder. Codes 0 and 1 mean success and a request or test failure, respectively. See the CLI reference.
My JSON report has no response bodies
The json reporter strips response bodies and redacts sensitive headers by default so the output is safe to share. Add --include-body and --include-secrets when you need the full payload.
Where is my data, and how do I reset it?
Everything lives in a single SQLite file. On Linux it is at ~/.local/share/com.ironcall.desktop/ironcall.db, on Windows at %APPDATA%\com.ironcall.desktop\ironcall.db. Quit Ironcall and remove or move that file to start from a clean state. See Privacy & Data.