An API testing tool your whole team can readFunctional checks and load, in plain words
Give BitAssure your API's address, then write each call and what its response should say. It runs the calls in order, carrying values from one to the next, on a schedule, from CI or under load, and reports every check in plain words.
No card needed.
- The status is 201
- $.status is "PAID"
- The order id is in the response
- Answered within 800 msAnswered in 1,340 ms instead
Every call, and what its response should say
A flow is a list of calls in order, each with the checks on its response. Each check is judged on its own, so one wrong field never hides the rest.
The status is 201
The status
Exactly a code, such as 201 or 401, or any success. A check that a refused request is refused counts as much as one that a good one works.
$.status is "PAID"
Fields in the JSON
The value at a path equals what it should, or something is there at all, for an id nobody can predict. Text anywhere in the body, too.
Content-Type is application/json
Headers
A named response header equals what it should: a content type, a cache rule, a version your clients depend on.
Answered within 800 ms
How long it took
A call comes back within the time you set, so an endpoint that slowed down fails before your users notice it.
Written once, run as often as it is worth running
The base address is the platform; each call is a method, a path, headers and a body, the way anyone who has used an API client already describes one.
Values carried forward
Take a token or an id out of one response and use it in the next call as {{token}}, so anything behind a sign-in can be tested.
A new value each run
Generated ids, timestamps, random numbers and text, drawn once per run and remembered, so "register, then sign in as that person" just works.
Credentials kept safe
A bearer token, an API key in a header of your choosing, or a username and password, stored encrypted and never shown again once saved.
On a schedule, or from CI
Hourly, daily, every weekday or weekly on every plan, or from your pipeline with an API key, with results as JUnit your CI already reads.
Under load
Run the same flow as many virtual users, ramped in, and read percentiles, errors and throughput per call and for the flow as a whole.
A report anyone can read
Every call and every check, pass or fail, as a page or a PDF, in plain sentences rather than a wall of JSON.
What it does not do, so you can plan around it
- A request body is one text field, read as JSON. Form and file uploads are not supported yet.
- Credentials are a bearer token, a header key or a username and password. OAuth client credentials are not built yet.
- Checks compare for equality, presence and timing. Patterns, number ranges and JSON schemas are not built yet.
- There is no import from Postman, cURL or OpenAPI yet: calls are added one at a time.
- The API has to be reachable from the internet. Testing one that is only inside your network, through a connector, is not built yet; websites can already be tested that way.
- A load test may only address your platform's own registered address, and its users and length are capped per account.
One credit a run, however many calls are in it
A functional API run costs one credit, $1.75 on pay as you go before tax. A load test is one credit per 50 virtual-user minutes. Every account starts with 50 free credits.