RestTesterConfigure your testplan
Set the base URL, authentication, timeouts, and runtime variables in one place.
A workspace for your API tests
Your API changes.
Your confidence
shouldn’t.
Build repeatable API tests, connect your requests, and see what passes—and why something fails. All in one clear workspace.
30 days to explore · No credit card required
Customer API
Your customer journey, covered.
Testplan confighttps://api.example.com
Tests 44 enabled
Run by tag
POST
Create a customer
smoke/customersGET
Get customer details
smoke/customers/${customerId}PATCH
Update the customer
regression/customers/${customerId}DELETE
Delete the customer
regression/customers/${customerId}↳ Try a tag to choose which example tests run.
✓ Repeatable testplans↔ Connected requests⌁ Live job output▥ Results over time
From request to result
More than sending a request.
A repeatable way to test your API.
Keep the setup, checks, and results together, so the next run starts with what you’ve already built.
01 / BUILD & CONNECTTest the whole flow,
Test the whole flow,
one request at a time.
Create a customer, capture its ID, and use it in the next request. Runtime variables let your tests follow the same journey as your application.
- Configure methods, endpoints, authentication, headers, query parameters, and JSON bodies.
- Check response values with JSON paths, comparisons, regex, and JSON Schema.
- Capture response values for later steps and tests. Run with imported CSV or JSON data.
Endpoint
/customers/${customerId}
Base URL inherited from testplan config
Check the response status
STATUSExpected status 200
Check a response value
$.id equals ${customerId}
Save a value for the next test
$.email → ${customerEmail}
HeaderValue
Acceptapplication/jsonX-Customer-ID${customerId}Reuse runtime values in headers as well as endpoints, parameters, and request bodies.
Runtime variableSource
customerIdCaptured from $.idcustomerEmailCaptured from $.emailDefine variables in your testplan config, then capture values from earlier responses.
1
Running Customer API2GET /customers/423Response: 200 OK · 184 ms4PASS Response status equals 2005FAIL Check response value at $.active6 Expected: true7 Actual: false8Authorization: [REDACTED]02 / RUN & INVESTIGATESee what happened.
See what happened.
Find what needs fixing.
Follow output as a job runs, then return to its results when you’re ready. Turn on debug mode when you need a closer look at a failed check.
- Watch sequenced output stream into a terminal with line numbers and scroll controls.
- Inspect request details and expected-versus-actual comparisons for failed checks.
- Keep credentials and variables marked Secret redacted in debug output.
03 / REVIEW & IMPROVEA single run tells you what happened.
A single run tells you what happened.
Your history shows the bigger picture.
Review recent jobs, spot failed runs, and track test success across a timeframe you choose. Come back to the output behind each result.
Jobs in period28Recent testplan runs
Test pass rate96.4%Passed / (passed + failed)
Test success rate100%
MonTueWedThuFriSatSun
A straightforward workflow
Set it up once. Build on every run.
Add the requests that matter
Define your checks, order the tests, and use tags to run a focused subset.
Run, review, repeat
Follow the job live, investigate failures, and revisit results from your dashboard.
Room for your next test
Start small. Grow your coverage.
Explore RestTester with a 30-day trial. These are the current capacity limits for each tier.
Start here
30-day trial
Get your first API flow covered.
Free for 30 days
- 1 testplan
- 10 total tests
- 30 job runs total
No credit card required
Individual projects
Personal
More coverage for your own APIs.
Pricing coming soon
- 3 testplans
- 50 total tests
- 100 job runs per day
Paid upgrades coming soon
Growing applications
Small business
Keep more API workflows in view.
Pricing coming soon
- 10 testplans
- 200 total tests
- 250 job runs per day
Paid upgrades coming soon
Larger test suites
Enterprise
Space for broader API coverage.
Pricing coming soon
- 50 testplans
- 2,000 total tests
- 1,000 job runs per day
Paid upgrades coming soon
Test limits are totals across your account, including disabled tests. The trial includes 30 job runs in total, with no daily reset. Paid tiers have daily job allowances that reset at 00:00 UTC. New accounts start on the trial; online payment and paid upgrades are not yet available.
A few helpful details
Before your first run.
Can one test use a value from another response?
Yes. Define a runtime variable in your testplan config, capture a response value with a JSON path such as $.id, and use ${customerId} in later requests or response checks.
Can I run only some of the tests in a testplan?
Yes. Add tags to individual tests, then select the tags in your testplan config. Only enabled tests matching a selected tag run. Clear the tag selection to include all enabled tests.
Can I try different data without duplicating my tests?
Import CSV or JSON data into your testplan to supply runtime variables for different data rows. Reuse the same requests and response checks across those inputs.
What can I see when a check fails?
Each job keeps its output and test results. Debug mode adds request details and redacted expected-versus-actual comparisons for failed checks. Authentication credentials and variables marked Secret are hidden in debug output.
Your next request, with more confidence
Make your API checks
part of the workflow.
Start with one testplan. Build a clearer picture with every run.