API QA: market
Data as of November 19, 2026: 38 open API QA jobs, 58% remote among jobs that state a work format. Source: Zorky, updated daily.
API QA — API testing engineer: checks software interfaces (REST, GraphQL, gRPC, SOAP) — the layer through which services and clients exchange data. In modern architecture of microservices and separate frontend / mobile clients API is the central testing layer: by the "testing pyramid" specifically API / integration tests make up the bulk of automated tests — they're faster and more stable than UI tests but check real business logic deeper than unit tests. API QA is responsible for contract correctness, error handling, validation, authentication and integration of services between each other. Role family: API QA Engineer (general — functional API testing), API Automation Engineer (focus on API autotests), Backend QA (server-side testing, special case — API testing), Integration QA (testing of service interactions). Stack 2026: Postman (dominant tool — manual requests, collections, tests; Newman — run collections in CI), REST Assured (API automation on Java — classic), pytest + requests / httpx (automation on Python), Karate (BDD framework for API), Bruno (open-source alternative to Postman, growing 2024–2026), Insomnia, SoapUI / ReadyAPI (including SOAP legacy). Contract testing: Pact (consumer-driven contracts — check that services don't break each other). Specifications and validation: OpenAPI / Swagger, JSON Schema, Schemathesis (property-based tests from OpenAPI spec). Mocks: WireMock, Prism, Mountebank. Adjacent: SQL and data verification in DB, Charles / Postman for traffic debugging, CI/CD, Git, knowledge of HTTP, response codes, methods, authentication (OAuth / JWT / API keys). Top stack: postman, python, agile, ci/cd, rest. Among jobs with a stated work format, 58% are remote. API QA — one of the most practical and in-demand QA specializations: microservice architecture made API testing the core of automation.
Data as of:
Key numbers for the API QA market: open jobs, median salary, observed talent pool and remote share.
The API QA market currently has 38 open roles, 35 of them freshly observed.
Among jobs with a stated work format, 58% are remote. API QA — one of the most remote-friendly QA specializations (all work with API, code, CI/CD, DB — no location binding).
⚠ salary known for 3 of 38 jobs; remote share from 31 with a stated format; 35 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many API QA postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 2 |
| 2026-06-08 | 0 |
| 2026-06-15 | 0 |
| 2026-06-22 | 7 |
| 2026-06-29 | 4 |
| 2026-07-06 | 13 |
| 2026-07-13 | 3 |
| 2026-07-20 | 3 |
| 2026-07-27 | 2 |
| 2026-08-03 | 3 |
| 2026-08-10 | 2 |
| 2026-08-17 | 2 |
| 2026-08-24 | 4 |
| 2026-08-31 | 0 |
| 2026-09-07 | 6 |
| 2026-09-14 | 3 |
| 2026-09-21 | 4 |
| 2026-09-28 | 5 |
| 2026-10-05 | 7 |
| 2026-10-12 | 13 |
| 2026-10-19 | 10 |
| 2026-10-26 | 8 |
| 2026-11-02 | 8 |
| 2026-11-09 | 4 |
Active sources per week
Sources over the period: 41. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 1 |
| 2026-06-08 | 0 |
| 2026-06-15 | 0 |
| 2026-06-22 | 4 |
| 2026-06-29 | 4 |
| 2026-07-06 | 3 |
| 2026-07-13 | 1 |
| 2026-07-20 | 3 |
| 2026-07-27 | 2 |
| 2026-08-03 | 3 |
| 2026-08-10 | 2 |
| 2026-08-17 | 2 |
| 2026-08-24 | 4 |
| 2026-08-31 | 0 |
| 2026-09-07 | 5 |
| 2026-09-14 | 3 |
| 2026-09-21 | 4 |
| 2026-09-28 | 5 |
| 2026-10-05 | 7 |
| 2026-10-12 | 5 |
| 2026-10-19 | 8 |
| 2026-10-26 | 5 |
| 2026-11-02 | 8 |
| 2026-11-09 | 3 |
New sources connected: Jun 22 +4 · Jun 29 +4 · Oct 19 +4 · Nov 2 +5 · all weeks (17) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 22 | +4 | 7 |
| Jun 29 | +4 | 4 |
| Jul 6 | +2 | 13 |
| Jul 13 | +1 | 3 |
| Jul 20 | +2 | 3 |
| Jul 27 | +1 | 2 |
| Aug 3 | +1 | 3 |
| Aug 17 | +2 | 2 |
| Aug 24 | +1 | 4 |
| Sep 7 | +3 | 6 |
| Sep 21 | +2 | 4 |
| Sep 28 | +1 | 5 |
| Oct 5 | +3 | 7 |
| Oct 12 | +3 | 13 |
| Oct 19 | +4 | 10 |
| Oct 26 | +1 | 8 |
| Nov 2 | +5 | 8 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 2 | 1 |
| 2026-06-08 | 0 | 0 |
| 2026-06-15 | 0 | 0 |
| 2026-06-22 | 7 | 4 |
| 2026-06-29 | 4 | 4 |
| 2026-07-06 | 13 | 3 |
| 2026-07-13 | 3 | 1 |
| 2026-07-20 | 3 | 3 |
| 2026-07-27 | 2 | 2 |
| 2026-08-03 | 3 | 3 |
| 2026-08-10 | 2 | 2 |
| 2026-08-17 | 2 | 2 |
| 2026-08-24 | 4 | 4 |
| 2026-08-31 | 0 | 0 |
| 2026-09-07 | 6 | 5 |
| 2026-09-14 | 3 | 3 |
| 2026-09-21 | 4 | 4 |
| 2026-09-28 | 5 | 5 |
| 2026-10-05 | 7 | 7 |
| 2026-10-12 | 13 | 5 |
| 2026-10-19 | 10 | 8 |
| 2026-10-26 | 8 | 5 |
| 2026-11-02 | 8 | 8 |
| 2026-11-09 | 4 | 3 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just API QA.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open API QA jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 38 |
| Open demand | 38 |
| Observed supply | — not published |
API QA — one of the most in-demand and fast-growing QA specializations. Driver 2026 — ubiquitous microservice architecture: the more services and integrations, the more critical systematic API testing; by testing pyramid API tests make up the bulk of automation. Demand is wide and stable.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
Which countries have the most open API QA jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| India | 9 | 24.3% |
| Poland | 6 | 16.2% |
| United States | 5 | 13.5% |
| Spain | 3 | 8.1% |
| Ukraine | 2 | 5.4% |
| United Kingdom | 2 | 5.4% |
| Singapore | 2 | 5.4% |
| Thailand | 1 | 2.7% |
| Cyprus | 1 | 2.7% |
| Malaysia | 1 | 2.7% |
| Other countries | 5 | 13.5% |
Leader by API QA job count — India (9 positions). Demand wide — banks / fintech, marketplaces, ecosystems, SaaS and B2B products, telecom, logistics. International companies hire Russian-speaking Senior API QA on full-remote.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| IN | 9 |
| PL | 6 |
| US | 5 |
| ES | 3 |
| UA | 2 |
| GB | 2 |
| SG | 2 |
| TH | 1 |
| CY | 1 |
| MY | 1 |
Which technologies are most often required in the same job as API QA.
Used together with
Share — how many of the 38 jobs in the API QA market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top stack API QA 2026: Postman (dominant — manual testing + Newman for CI), REST Assured (Java automation), pytest + requests / httpx (Python), Karate (BDD for API), Bruno (open-source, growing), SoapUI / ReadyAPI; contract testing — Pact; specifications — OpenAPI / Swagger, JSON Schema, Schemathesis; mocks — WireMock, Prism; plus SQL, CI/CD, Git, knowledge of HTTP / REST / GraphQL / gRPC and authentication.
Common pairs: Postman + Newman (manual + CI), REST Assured + Java + JUnit / TestNG, pytest + requests + Python, Karate + BDD, Pact for contract testing. Learning roadmap: QA basics → HTTP thoroughly → Postman → JSON / OpenAPI → authentication → SQL → programming language → automation (REST Assured or pytest) → CI/CD → mocks and contract testing → pet project.
Chart data
| Name | Count |
|---|---|
| java | 13 |
| postman | 11 |
| sql | 8 |
| jenkins | 6 |
| junit | 6 |
| cloud | 5 |
| selenium | 5 |
| playwright | 5 |
| api testing | 4 |
| python | 4 |
| testng | 3 |
| aws | 3 |
How many API QA jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 9 |
| middle | 6 |
| lead | 1 |
| junior | 1 |
Career flow: manual QA → API QA → API Automation → Senior → SDET / general Automation, or (rarer) transition to backend development — API QA gives a good base. API Automation is valued noticeably higher than manual API testing.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 9 |
| middle | 6 |
| lead | 1 |
| junior | 1 |
Who hires the most for API QA and how concentrated demand is among the largest companies.
Employers
Demand is spread across 30 employers. The largest accounts for 16.2%, the top ten for 46.0%; the remaining 54.0% is long tail.
| share | value |
|---|---|
| top-1 | 16.2% |
| top-3 | 27.0% |
| top-10 | 46.0% |
| long tail | 54.0% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects API QA jobs from.
Where Zorky sees this market
Observed across 18 sources; the largest accounts for 15.8% — this market does not rest on a single channel.
API QA vacancies: hh.ru, Habr Career, getmatch, Djinni, LinkedIn, Telegram (QA and automation channels). Real market significantly wider than exact search — API testing is part of most «QA Automation», «Backend QA» and «SDET» vacancies, not always designated by separate term «API QA».
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| board | джоб-борды и агрегаторы | job boards & aggregators | 20 | 0.5263 |
| ats | ATS и карьерные сайты | ATS & career sites | 18 | 0.4737 |
The newest API QA jobs from company career sites.
Recent openings
- Backend QA · IN
- Test Lead - API Automation · IN
- Automation QA Engineer (API / Cloud) · UA
- […] - Senior QA Engineer - API Testing - Insurance Domain · IN
- Automation Engineer 4 (SDET/API automation) · US
- API Testing Engineer - RestAssured/Selenium · IN
- API Test Engineer · US · $11,666
- Senior Automation Testing Engineer (4- 6 years, Selenium, API Testing, Cloud and Git/Jenkins) · IN
Latest open API QA jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.
Adjacent markets
API QA borders backend development (API testing — closest to backend part of QA, common bridge into development), general QA Automation and SDET. Overlaps with Security QA (API security testing) and Performance (API load). Comparison of QA specializations — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 9.
Direction: QA / Testing
Related specializations
Inside API QA: API QA Engineer (general — functional API testing), API Automation Engineer (focus on autotests — valued higher), Backend QA (server-side testing, special case — API), Integration QA (testing of service interactions). Adjacent QA specializations — Automation, SDET. Comparison — in the bar below.
Frequently asked questions
The most common questions about API QA: pay, grades, tools (Postman vs REST Assured vs Karate vs pytest), testing REST / GraphQL / gRPC, contract testing (Pact), remote, companies, how to start, Senior skills. Answers recompute automatically.
What tools are most often required from API QA?
Top-5: postman, python, agile, ci/cd, rest. Manual testing and API exploration: Postman (dominant — requests, collections, environments, built-in tests; Newman — running collections in CI), Bruno (open-source alternative, on git files — growing), Insomnia, SoapUI / ReadyAPI (including SOAP). Automation: REST Assured (Java — classic of API autotests), pytest + requests / httpx (Python — popular stack), Karate (BDD framework for API in Gherkin), Playwright API testing, supertest (Node.js). Contract testing: Pact (consumer-driven contracts). Specifications and validation: OpenAPI / Swagger, JSON Schema, Schemathesis (test generation from OpenAPI spec). Mocks: WireMock, Prism, Mountebank. Adjacent: SQL (check that data correctly landed in DB), CI/CD, Git, Docker. Knowledge: HTTP (methods, status codes, headers), REST / GraphQL / gRPC, authentication (OAuth 2.0, JWT, API keys), formats (JSON / XML), API design principles. For automation a programming language is mandatory — more often Java or Python.
Postman vs REST Assured vs Karate vs pytest — what to choose?
Postman — standard for manual exploration and quick API check: convenient GUI, collections, environments, can write tests in JavaScript; through Newman collections run in CI. Downside as automation framework — tests in JSON collections scale and version worse than code. REST Assured — Java library, classic of API automation: expressive given-when-then DSL, easily integrates with JUnit / TestNG and Java ecosystem; choice if team and project on Java. pytest + requests / httpx — Python stack: flexible, laconic, low entry threshold, huge pytest ecosystem (fixtures, parametrization, plugins); choice of Python teams. Karate — self-contained BDD framework for API: tests written in Gherkin-like syntax, doesn't require Java knowledge for writing tests, built-in JSON checks, mocks, load testing; good when need to connect less technical people to API tests. Strategy: Postman — must know (it's everywhere, for manual work and quick check). For automation — by team stack: REST Assured (Java projects), pytest (Python projects), Karate (if low threshold and BDD matter). Tool is secondary — primary are understanding of HTTP, API architecture and skill of writing maintainable tests.
How does testing REST, GraphQL and gRPC differ?
REST — the most widespread API style: resources by URL, HTTP methods (GET / POST / PUT / DELETE), status codes, usually JSON. Testing — checking endpoints, methods, response codes, request / response bodies, error handling, validation; tools — Postman, REST Assured, pytest. GraphQL — one endpoint, client describes in the query what fields they need. Testing features: checking schema and resolvers, that exactly needed fields are requested, handling partial errors (GraphQL can return 200 with errors array), depth and complexity of queries (protection from heavy queries), N+1 problems. Tools — Postman (supports GraphQL), Apollo tools, specialized clients. gRPC — binary protocol based on Protocol Buffers over HTTP/2, popular for communication between microservices. Features: contract is set by .proto files (strict typing), special clients needed (grpcurl, Postman supports gRPC, BloomRPC), unary and streaming calls are tested. SOAP — legacy (XML, WSDL), still encountered in enterprise and banks; tool — SoapUI / ReadyAPI. Common: regardless of protocol, API QA checks contract, business logic, error handling, security and integration. Transport, format and tools differ — but test design principles are the same.
What is contract testing (Pact) and why is it needed?
Contract testing solves a typical pain of microservice architecture: service A ("consumer") calls service B's ("provider") API; team B changes its API — and imperceptibly breaks A; full-fledged end-to-end tests of all services together are slow, fragile and hard to maintain. Pact — the most well-known consumer-driven contract testing tool. Idea: consumer team describes their expectations from provider API in the form of a "contract" (pact file) — what requests they send and what responses they expect. This contract is published (in Pact Broker). Provider in their pipeline runs tests against all contracts of their consumers — and immediately sees whether their change broke any of them. At the same time services are tested separately (fast, stable), without raising the whole system. Why API QA: contract testing catches integration regressions early and cheaply, without fragile end-to-end tests; mature practice often implemented by QA engineers. In modern microservice products knowledge of Pact / contract testing — a strong skill of Senior API QA. Complements (doesn't replace) functional API testing and targeted end-to-end checks of key scenarios.
What share of jobs are remote?
Among jobs with a stated work format, 58% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How to start an API QA career in 2026?
API QA — practical and in-demand specialization, good entry into more "engineering" testing. Roadmap: 1) QA basics — test design, types of testing, bug reports. 2) HTTP — thoroughly: methods (GET / POST / PUT / PATCH / DELETE), status codes (2xx / 3xx / 4xx / 5xx), headers, cookies, request / response body; what REST is. 3) Postman — master as main tool: requests, environments, variables, collections, writing tests, running through Newman. 4) Formats and validation — JSON (and XML), JSON Schema, reading OpenAPI / Swagger specifications. 5) Authentication — OAuth 2.0, JWT, API keys, basic auth — how to test protected endpoints. 6) SQL — mandatory: check that the request correctly changed data in DB. 7) Programming language — for automation one needed: Java (then REST Assured) or Python (then pytest + requests). 8) API automation — write a set of autotests with the chosen framework, figure out fixtures, parametrization, reports. 9) CI/CD — running API tests in pipeline. 10) Advanced — mocks (WireMock), contract testing (Pact), GraphQL / gRPC. 11) Pet project: take an open API, write functional autotests, connect to CI. Resources: Postman documentation, learning APIs (e.g. open public APIs for practice), testing schools (Otus, «QA Automation» courses), books and materials on API testing. API Automation is valued noticeably higher than manual — move toward automation and master code.
How many open jobs are in this sample?
The published sample contains 38 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior API QA need?
Senior API QA owns testing of software interfaces at engineering level. HTTP and protocols: deep understanding of HTTP, REST, GraphQL, gRPC (and SOAP in legacy), semantics of methods and status codes, caching, idempotency. API design: understanding of good API principles (versioning, pagination, error handling, consistency) — to see not only implementation bugs but design problems. Production-level automation: designing API autotest architecture (REST Assured / pytest / Karate), reusable layers (clients, request builders, checks), test data management, test isolation, fighting instability. Contract testing: Pact / consumer-driven contracts — for microservice integrations. Microservice testing: understanding what and at what level to check (testing pyramid), integration scenarios, mocks and stubs (WireMock), testing asynchronous interactions (queues, events). Specifications: OpenAPI / Swagger, schema validation, generative tests (Schemathesis). SQL and data: confident DB state checks, understanding of data integrity. Authentication and security: OAuth / JWT, basic API security testing (OWASP API Security Top 10). Programming: confident code in automation language, clean maintainable test code, code review. CI/CD: integration of tests in pipeline, test gates, parallel run, reporting. Infrastructure: Docker, environments understanding. Soft: mentoring, building API testing process in the team, communication with development. English — for international market and documentation. Senior API QA is essentially an engineer, and this specialization — one of the closest to backend development inside QA.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.