■ API Mocking
Mock any API in minutes, without writing a single line of backend.
Define rules by method and path, use templating to generate dynamic responses, and get a testable URL right away — no server to spin up, no database to configure.
Mocking an API the manual way
- A hand-built stub server, or a static JSON file that never reacts to anything in the request
- No easy way to simulate different responses for the same endpoint (success, error, empty)
- Sharing the mock with your team means "here's the zip" or a service that needs heavy setup
- Testing a stateful flow (create → list → update) means building a whole fake backend
With httpdrop
- Mock Rules by method + path, with route params (
/users/{id}) and wildcards - Response body and status with Handlebars templating — conditional on header, query, or request body
- Response Sequences and weighted responses to simulate real variation between calls
- Automatic stateful CRUD: spins up a simulated table with real persistence between calls, no code needed
- Shareable URL as soon as the rule is saved
How it works
1
Create an endpoint
An endpoint is your mock domain — gets its own subdomain or a short URL.
2
Define the Mock Rule
Method, path (with params), status, and response body.
3
Add logic if you need it
Conditional templating, response sequence, delay, or required body.
4
Test it live
Call the URL from Postman, curl, or your app — the response is already live.
5
Go stateful if the flow needs it
Automatic CRUD keeps real state across calls (create, list, update, delete).
What httpdrop API Mocking is
- Contract simulation: request and response in the right shape, with real conditional logic
- Fits the workflow you already use — Postman, Insomnia, curl, code
What it isn't
- Not a production backend — it's a simulation layer for development and testing
- Not a substitute for real load testing against your own infrastructure
Use cases
Frontend before the backend is ready
Frontend teams build against the agreed contract without waiting on the backend to ship.
Automated test fixtures
QA and CI use deterministic or sequenced responses, without depending on an unstable external service.
Mocking third-party APIs
Simulate an external provider (payments, geolocation) without burning real quota during development.
FAQ
Is it free?
Yes — the free plan includes enough endpoints and Mock Rules to get started, no credit card required.
Can I simulate different responses for the same endpoint?
Yes — Response Sequences (one response per call, looping or stopping at the last) and Weighted Responses (probability-based variation).
Does the mock remember what I created in a previous call?
With automatic CRUD, yes — each simulated table persists across calls, like a real database.