Mock API
Paste the JSON an API should return and get a real URL to test your frontend against.
The JSON, HTTP status and delay you configure are sent to the Nexinon server and stored until the mock expires or is deleted — it's the server that answers the public URL for any client, not your browser. The management token, returned only at creation, is stored only as a hash (never in plain text) — the server cannot recover it afterwards.
Any code between 100 and 599.
Just a reminder for yourself when you come back later — there's no account system, so this is the only way to note it.
How Mock API works
Paste the JSON an API should return and the tool generates a short, real URL (nexinon.dev/mock/<id>) that starts serving exactly that content — with the correct Content-Type and open CORS, so any frontend under development, third-party app (Postman, Insomnia) or script (curl) can call it for real, from any origin. It's deliberately simple: one URL maps to a single fixed response. Multiple routes or different responses per path aren't part of this version — the goal is having something working in seconds, not rebuilding a full API server.
HTTP status and simulated delay
Besides the JSON, you choose the response's HTTP status (any code between 100 and 599, with shortcuts for the most common ones) and a simulated delay before responding, from 0 to 5 seconds. This lets you test not just the happy path of a screen, but also the sad path — how your frontend reacts to a 404, a 500, or a slow response — without the real backend needing to exist yet or be deliberately made unstable. The mock responds the same way to GET, POST, PUT, PATCH or DELETE: the configured status, body and delay always come out the same, regardless of the HTTP method used.
Editing and deleting a mock
When you create a mock, you also get a management link and a management token — shown only once, never recoverable afterwards. The management link opens a page where you can change the JSON, status, delay or label, renew the expiration, or delete the mock for good, always using the token as credential. Lost the management link? There's no way to recover it — the only way out is to create another mock.
Frequently asked questions
No. The mock returns the same configured response regardless of the HTTP method used — the same status, the same body and the same delay come out for GET, POST, PUT, PATCH and DELETE. Simulating different responses per method is out of scope for this version.
Yes — HTTP status (any code between 100 and 599) and simulated delay (up to 5 seconds) are configurable from creation, exactly to test your frontend's sad path and loading states, not just the happy path.
Yes, always — every mock has a validity period, from 1 hour to 30 days (default 7 days). There's no "never expires" option. You can renew the validity at any time from the management page, without having to recreate the mock.
There's no way to recover it, by design: the server only stores a hash of the token, never the original value. The only way out is to create a new mock. Save both carefully as soon as the mock is created — they only appear once.
Practically impossible — the URL's identifier has 128 bits of randomness, the same pattern used by Secret Share. That said, the public URL has no password: anyone with the link can call it, which is expected (that's what it's for).
That's not the goal. It's a development and prototyping tool — for testing a frontend before the real backend exists, validating collections, or teaching how an API responds. A mock expires, has no availability guarantee, and doesn't replace a real backend.