HTTP status codes for API testing
Look up HTTP status codes such as 200, 201, 401, 403 and 404, with QA review points. Interpret actual responses against your API specification.
Look up status codes →- No account or installation
- Copy or download results
- Documents processed in your browser
File sizes and generation counts have limits. Check the limits shown in each tool.
Worked example · fictional specification
Review responses from a user lookup API
Assume that you are reviewing an API that reads user information. Check the response body, authentication, authorization and resource existence as well as the status code.
1. Enter data
Search: 401 Compare: 200 / 401 / 403 / 404
- Search HTTP status codes by number or meaning.
- Compare the meaning and QA review point with the actual specification.
- Test valid/expired tokens, an account lacking permission and a missing resource; record codes and response bodies.
2. Read the result
| Code | Meaning | QA review point (Korean tool output) |
|---|---|---|
| 200 | OK | 응답 모델과 실제 데이터 확인 |
| 201 | Created | 리소스 생성과 Location 확인 |
| 204 | No Content | 빈 응답과 클라이언트 처리 확인 |
| 401 | Unauthorized | 미인증/만료 토큰 검증 |
| 403 | Forbidden | 인증된 계정의 권한 부족 검증 |
| 404 | Not Found | 없는 리소스와 노출 정책 검증 |
| 429 | Too Many Requests | 제한과 Retry-After 확인 |
| 500 | Internal Server Error | 서버 오류와 정보 노출 여부 |
Swipe the table sideways to see all columns.
3. Use it in your tests
Generally, 401 indicates missing valid authentication and 403 indicates refusal to fulfill the request. Services can use 404 to hide resource existence, so define the expected code from the specification.
Limits and additional checks
Do not treat 200 alone as a pass: inspect the body and actual read/write effects. This tool is a reference table; it neither sends API requests nor monitors a server.
View the tool screen
Download the example table (CSV)Download the input example (TXT)
Written and checked against the tool by QA Workbench · 2026-10-14. Fictional inputs; this is not a record of tests run against a service.
HTTP Semantics (RFC 9110) · 429 Too Many Requests (RFC 6585)