Start here
Coming from Postman
Bring your Postman collections, environments and scripts across in a minute, and find where each Postman feature lives in APITestCenter.
Your Postman collections come across as they are: folders, requests, auth, {{variables}}, environments and the pm.* scripts. Nothing is uploaded anywhere, and no account is needed.
Bring your work across
- In Postman, export each collection: ⋯ next to the collection → Export → Collection v2.1 → Export. Export each environment too: Environments → ⋯ next to it → Export.
- In APITestCenter, click Import (the arrow icon in the Saved requests panel) and choose the files, several at once if you like. Collections and environments can come in together.
- Check the list of what was found, and anything that couldn't come across, then press Import.
From a terminal, atc import my-collection.json does the same (CLI and CI).
What comes across
| From Postman | In APITestCenter |
|---|---|
| Collections and folders | Collections and folders, in the same order |
| Requests: params, headers, bodies (raw, form, GraphQL, files) | The same. A form's files aren't in a Postman export: choose each one again on the Body tab (the import says which) |
| Auth: Bearer, Basic, API key, Digest, NTLM, OAuth 1.0, AWS Signature, JWT | The same auth |
| OAuth 2.0 | Enter its settings again on the Auth tab |
| Auth and variables on a collection or folder | That folder's settings, inherited by its requests |
| Environments | Environments, with {{variables}} working as they did |
| Saved example responses | Each request's Example (the first successful one), which the mock server answers with |
| Pre-request and test scripts | Scripts, on the same folder or request. pm.test, pm.expect, pm.environment, pm.variables, pm.sendRequest and the older tests[…] run as they are |
Secret values in an environment (tokens, passwords) are encrypted on your computer. Type them once after the import if the export left them empty.
Where things are
| In Postman | In APITestCenter |
|---|---|
| Send a request | Test API: the same request bar, Send (Ctrl+Enter) |
| Tests tab | Checks for no-code rules (status, a JSON field, a header, time), or Scripts for pm.test |
| Collection Runner | Run collection: every request in order, with what passed (Run a collection) |
| Monitors | Scheduled checks on the Run collection page, while the app runs, or a CI pipeline for around the clock |
| Newman in CI | atc suite <collection> fails the build when a request fails (From the app to your pipeline) |
| Performance testing | Run performance test: real load from your computer with k6, goals, and a report that says whether it held up (Performance tests) |
| Mock servers | Mock server in the status bar, on your own computer (Mock server) |
| Workspaces | Projects: a folder each, so a project can live in Git or a synced folder (Working in the app) |
| Postman Flows, Vault, Visualizer | Not in APITestCenter. Chain requests with Run first and Save values instead of Flows |
What's different
- Everything stays on your computer. Requests go from your computer straight to your API, so internal and VPN-only APIs work, and nothing about them reaches us. There's no cloud workspace: share a project through Git or a synced folder, or export a collection.
- Load tests are built in. Any saved request is a performance test one click away, with presets (smoke, load, stress, spike, soak) and a plain-language verdict.
- No account is needed. Signing in is optional and only carries a paid plan.
Something didn't come across as you expected? Write to support@apitestcenter.com with the part of the export that didn't work, and we'll fix the importer.