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

  1. In Postman, export each collection: ⋯ next to the collection → Export → Collection v2.1 → Export. Export each environment too: Environments → ⋯ next to it → Export.
  2. 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.
  3. 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 PostmanIn APITestCenter
Collections and foldersCollections 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, JWTThe same auth
OAuth 2.0Enter its settings again on the Auth tab
Auth and variables on a collection or folderThat folder's settings, inherited by its requests
EnvironmentsEnvironments, with {{variables}} working as they did
Saved example responsesEach request's Example (the first successful one), which the mock server answers with
Pre-request and test scriptsScripts, 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 PostmanIn APITestCenter
Send a requestTest API: the same request bar, Send (Ctrl+Enter)
Tests tabChecks for no-code rules (status, a JSON field, a header, time), or Scripts for pm.test
Collection RunnerRun collection: every request in order, with what passed (Run a collection)
MonitorsScheduled checks on the Run collection page, while the app runs, or a CI pipeline for around the clock
Newman in CIatc suite <collection> fails the build when a request fails (From the app to your pipeline)
Performance testingRun performance test: real load from your computer with k6, goals, and a report that says whether it held up (Performance tests)
Mock serversMock server in the status bar, on your own computer (Mock server)
WorkspacesProjects: a folder each, so a project can live in Git or a synced folder (Working in the app)
Postman Flows, Vault, VisualizerNot 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.

Something unclear or missing? Write to support@apitestcenter.com — the guide improves with every question.