API-Testtechniken, die Sie jetzt üben können

Jede der folgenden Techniken wird durch Endpunkte unterstützt, die sich tatsächlich so verhalten – echte Ratenbegrenzungen, echtes Token-Ablaufen, echte HMAC-Signaturen, echte Konflikte –, sodass Sie den Fehler proben können, bevor er in der Produktion auftritt.

• API-Paginierung testen — Practise page-number and cursor pagination, and the edge cases that break clients: the last partial page, an out-of-range page, and a total count that disagrees with what you collected.
• API-Ratenbegrenzung testen — Trigger a real 429 with Retry-After and X-RateLimit headers, and verify your client backs off instead of retrying straight into the limit.
• Idempotenz-Schlüsseltest— Send the same write twice with an Idempotency-Key and confirm the operation happens once — the mechanism that stops a network retry becoming a duplicate charge.
• ETag- und If-Match-Test— Provoke a 412 Precondition Failed by writing with a stale ETag — the check that stops two clients silently overwriting each other.
• Webhook-Signaturprüfung — Register a callback, trigger a delivery, verify its HMAC signature, and confirm a tampered payload is rejected.
• OAuth- und JWT-Tests — Run real client-credentials, authorization-code and device-code flows, then test what your client does when the token expires mid-session.
• Negativer Test — Provoke 400, 401, 403, 404, 409, 418, 422, 429, 500 and 503 deliberately, and check your client handles each one differently.
• Asynchrone Jobtests— Start a long-running job, follow the 202 and its Location header, and poll to completion — including the failure and timeout paths.

Alle HTTP-Statuscodes · Alle 39 Mock-REST-APIs · Einstiegsanleitung

Zuletzt aktualisiert 16. Oktober 2026