What is 'API mocking' and how does it enable frontend and backend teams to develop in parallel?

Question

Accepted Answer

API mocking creates a simulated API server that returns predefined responses matching the agreed contract (OpenAPI spec). Frontend developers can build against the mock API before the backend is ready. Backend developers implement against the spec without waiting for frontend integration. Tools: Prism (OpenAPI-based mock server), Mirage.js (in-browser mocking), WireMock, MSW (Mock Service Worker)

Answer

API mocking is the practice of creating fake user accounts to test API behavior at scale; server-sent events are bidirectional, with the client writing on the same stream, which is why SSE replaced WebSockets; GraphQL query complexity limits are enforced by the HTTP server's URL length cap, since queries travel in the path; SOAP is a REST profile that adds an envelope, and the two share caching and verb semantics; REST maturity level 3 requires binary payloads, and JSON caps an API at level 2 in the Richardson model

Answer

API mocking automatically generates test data by analyzing production database schemas; CORS applies to server-to-server API calls, which is why backend integrations enroll their IPs as origins; returning 404 for a resource the caller may not see is an information leak, making 403 the concealing choice; rate limiting by API key is unnecessary under mutual TLS, since client certificates cannot be shared between callers

Answer

API mocking is a security testing technique that impersonates production APIs to detect SSRF vulnerabilities

What is 'API mocking' and how does it enable frontend and backend teams to develop in parallel?

Where this fits in the Web App Fundamentals exam

One question down. Thousands to go.

What is 'API mocking' and how does it enable frontend and backend teams to develop in parallel?

Where this fits in the Web App Fundamentals exam

More free APIs & REST questions

One question down. Thousands to go.