REST, SOAP, and GraphQL in one editor
Set parameters, headers, body, and authorization in the request editor, send the request, and read the response without leaving Studio. GraphQL queries go in the request body.
Import your OpenAPI, Postman, or WSDL definitions, verify every response, and run the same API suite in CI, alongside your web and mobile tests.
Requests sit in a collection that someone runs by hand before a release. Nothing runs on its own, and nothing fails a build.
Turn requests into test cases with verifications, group them into suites, and run them from CI on every build.
A hand-built framework needs Java and a build tool to change one assertion, so testers wait on developers.
Testers add checks in the request editor and the manual view. Engineers script in Groovy or Java in the same project.
API checks run in one tool and UI tests in another, so nobody sees one picture of a release.
Mix API, web, and mobile steps in one test case, and see every run in one TestOps record.
Build requests, verify responses, drive them with data, and run them in CI, next to the rest of your tests.
Set parameters, headers, body, and authorization in the request editor, send the request, and read the response without leaving Studio. GraphQL queries go in the request body.
Import API definitions as ready-to-send requests, or generate positive, negative, and edge-case tests from an OpenAPI spec with AI (beta).
Check status codes, headers, JSON and XML values, and schemas with built-in keywords, or write your own assertions in Groovy.
Create an order through the API, then check it in the browser or the app, in the same test case and the same report. Set up test data through the API instead of clicking through the UI.
Bind CSV, Excel, or database data to a test suite and run the same requests for every row. Execution profiles switch base URLs and credentials per environment.
Run API suites headless with Katalon Runtime Engine in any CI system. Each run produces HTML, CSV, PDF, and JUnit reports, and results upload to TestOps.
Pick a pattern. Each snippet is the Groovy view of a Studio test case, so you can paste it in or build the same steps without code.
import static com.kms.katalon.core.testobject.ObjectRepository.findTestObject
import com.kms.katalon.core.webservice.keyword.WSBuiltInKeywords as WS
def response = WS.sendRequest(findTestObject('Object Repository/Transfers/POST create transfer',
[('amount') : 250.00, ('currency') : 'USD']))
WS.verifyResponseStatusCode(response, 201)
WS.verifyElementPropertyValue(response, 'currency', 'USD')Most teams already have API requests in a client tool or a code framework. Studio picks up from there instead of starting over.
Import Postman collections into the Object Repository as ready-to-send requests, then add checks, test data, and suites around them.
Engineers keep scripting in Groovy or Java with full IDE support. Testers work in the manual view on the same test cases, so nobody waits on anyone.
From fintech lending to telecom, QA teams cover APIs and UI in one framework.
Testing with Katalon Studio is truly easy to set up. It provides out-of-the-box integrations with other CI tools (Jenkins) to support our CI testing goal. We can custom test with TDD, BDD, DDT, and more.
Test management, test automation, test execution, and production insights, all unified in Katalon True, the AI platform for software quality.
Course
Guide
ComparisonStart a free trial of Katalon Studio, import an OpenAPI, Postman, or WSDL definition, and send your first verified request today.
API test automation sends requests to an API and checks the responses with code or a tool instead of by hand: status codes, response values, schemas, and response times. The tests run on every build, so a broken endpoint fails the pipeline before it reaches users.
Katalon Studio tests REST APIs (GET, POST, PUT, PATCH, DELETE, and more) and SOAP services (SOAP and SOAP 1.2). GraphQL queries are sent as the body of a REST request, over GET or POST, and mutations over POST.
Yes. Studio imports OpenAPI 3.0 and Swagger 2.0 files or URLs, Postman collections in v2.1 format, WSDL services, and SoapUI projects. Imported requests land in the Object Repository, ready to send and verify.
Use the verification snippets in the request editor, built-in keywords such as WS.verifyResponseStatusCode and WS.verifyElementPropertyValue, or your own Groovy assertions. Studio also validates JSON and XML responses against a schema, and checks responses against an OpenAPI specification.
The request editor supports Basic, Bearer, Digest, NTLM, OAuth 2.0, and AWS Signature. API collections let a folder of requests share one authorization setting.
Yes, in beta. Point Studio at an OpenAPI or Swagger specification and it generates positive, negative, security, and edge-case test cases that you review and keep in your project.
Run the test suite headless with Katalon Runtime Engine using the katalonc command, with -browserType="Web Service". It works in Jenkins, GitHub Actions, Azure DevOps, GitLab CI, Docker, and other CI systems, and results can upload to Katalon TestOps.
Many teams use both: Postman to explore an API, and Studio to turn those requests into maintained, data-driven test suites that run in CI and share reports with web and mobile tests. You can import Postman collections directly into Studio.