QAEverest Public API & Jira App — Frequently Asked Questions
What can the public API do? It is a versioned REST API at https://api.qaeverest.ai. It generates test cases, including API, UI and mobile tests, builds and runs automation suites and returns their results, runs security scans and performance tests, proofreads text, and reports your usage.
Where do I get an API key? In the app, open Profile → API Keys for a personal key. Developers building on the API can also create an API account at https://qaeverest.ai/api-client/signup. Keys start with qae_.
How do I authenticate? Send your key in the x-api-key header, or as Authorization: Bearer followed by the key.
How is API usage billed? Per unit, against your credits: for example per generated test case, per executed test case, or per scan. On an API account, GET /api/v1/usage returns your credits, your request allowance and the live rates. A call that is refused or returns an error is free. POST /api/v1/execute is charged when the run starts, per test case, so test cases that then fail still use credits.
What do the API's error codes mean? 402 means you don't have enough credits, or your plan is no longer active. 403 means the key isn't allowed: the service is switched off for your API account, the account or API user isn't active, or the key isn't tied to a QAEverest account. 429 means an API account has reached its monthly request limit, or too many AI agent or Check strength runs started through the API are still in progress.
Why did a long-running call return 200 with an error in it? After 40 seconds the server starts holding the connection open, which commits the 200 status, so a later failure arrives as success: false in a 200 response. Always check the success field, not only the status code.
What does QAEverest Test Generator for Jira do? It reads the summary and description of the Jira issue you're viewing, sends them to QAEverest's AI service, and generates structured test cases — titles, step-by-step actions, expected results, and priority. You can then push the generated test cases back into Jira as sub-tasks on the same issue.
How do I get started? 1. Create a free account at qaeverest.ai 2. Go to Profile → API Keys and generate a key (starts with "qae_") 3. Open any Jira issue, launch the QAEverest panel, and paste your API key into Setup 4. Click "Generate Test Cases"
What is the QAEverest API key, and is it required? Yes — it authenticates your requests to the QAEverest backend and tracks your credit balance. Without it, the app cannot generate test cases. Your key is stored locally in your browser; QAEverest's servers store only a one-way hash of it, never the raw key.
Is there a free tier? Yes, new accounts include a number of free generations. After that, you'll need an active paid plan on qaeverest.ai — the panel shows your remaining credit balance and prompts you to top up when you run out.
What Jira data does the app access? Only the summary and description of the issue you actively open the panel on, read on demand — the app does not continuously scan or bulk-export your Jira issues, and does not use your issue content to train AI models.
Where is my issue content processed? Your submitted issue text is sent from Atlassian's infrastructure to QAEverest's backend (api.qaeverest.ai) and its AI sub-processor to generate a result. See the full Privacy Policy for details.
Can I review test cases before they're added to Jira? Yes — generated test cases are shown in the panel first. You choose which ones to push; nothing is written to Jira automatically.
How are test cases added to Jira? Each approved test case is created as a Sub-task under the issue you generated it from, including steps, expected result, and priority in the description.
What if generation fails or times out? Generation runs as a background job and the panel polls for the result. If it returns an error, check that your API key is valid and that you have remaining credits. Persistent failures can be reported to support.
Does this work with Jira Service Management? The panel works on any Jira issue type, including service desk requests.
Is my data secure? All traffic to the QAEverest backend uses TLS encryption. The app only requests the minimum Jira scopes needed (read:jira-work, write:jira-work).