API Mocking vs API Interception: What's the Difference?
API mocking replaces the API with a fake. API interception edits real traffic as it passes. See the difference with diagrams, and when to use each.
Blog
Practical guides for seeing what your apps send, and for making them misbehave on purpose.
API mocking replaces the API with a fake. API interception edits real traffic as it passes. See the difference with diagrams, and when to use each.
AI-written code breaks at the network boundary. See how a network interceptor lets you edit API responses in transit, force errors and find bugs without touching the backend.
Make a real server answer "I'm a teapot" on demand. A silly status code that's secretly the best way to find out whether your app copes with errors it has never heard of.
Make a payment, login or search endpoint fail on demand, so you can see how your app handles errors. Two rules, no code changes, and one detail that keeps you from double-charging a card.
Make an endpoint hang, answer late, or fail after a delay, to check how your app behaves when the network is the problem rather than the server.
Use a Pause and Review rule to freeze matching requests before they leave your machine, change the method, URL, headers or body, and resume or drop them. A manual breakpoint for the network.