New in 2.4: Test runs you can trust See what's new →

Free fake APIs compared: what each one does with a write

The same requests sent to four free APIs, with the results and which one to pick.

Examples last run against the API on

Four free fake APIs answer most searches: JSONPlaceholder, DummyJSON, ReqRes and testingapis.com. None of them needed an API key for the requests below. They differ in what happens after a write, how they treat bad input and how much failure you can ask for. Pick JSONPlaceholder for tutorials and large read-only lists, DummyJSON for its shop-style data, ReqRes for quick user and login examples, and testingapis.com when your app has to read back its own writes or handle errors.

We run testingapis.com, so read this as a vendor's comparison. To keep it checkable, every row is a request we sent to the public API on 1 November 2026, and you can repeat each one. These services change, so test the row you depend on.

The results

CheckJSONPlaceholderDummyJSONReqRestestingapis.com
POST a record, then GET it404404404200, it was saved
POST an empty object201201201400 with a message
Delay a responseNo delay option in its guide?delay=1000?delay=2?delay=1
Ask for a 503No route found/http/503No route found/api/status/503 or ?error=503

"No route found" means we didn't find one in that service's public pages, so tell us if we missed it.

Do writes persist?

This matters as soon as a screen creates something and then lists it. With a simulated write, the create call succeeds and the record is missing on the next load, so you end up keeping it in local state just for the demo.

Terminal
# JSONPlaceholder: the POST answers 201, the record isn't there afterwards
$ curl -s -o /dev/null -w "%{http_code}" https://jsonplaceholder.typicode.com/posts/101
404

# DummyJSON: POST /products/add returned id 195
$ curl -s -o /dev/null -w "%{http_code}" https://dummyjson.com/products/195
404

# ReqRes: POST /api/users returned id 544
$ curl -s -o /dev/null -w "%{http_code}" https://reqres.in/api/users/544
404

# testingapis.com: POST /api/Posts returned id 24
$ curl -s -o /dev/null -w "%{http_code}" https://api.testingapis.com/api/Posts/24
200

What bad input does

The first three accept an empty object with a 201. That's fine for a happy-path demo, but your form's error branch never runs. Here, a missing required field gets a real 400:

Terminal
$ curl -i -X POST https://api.testingapis.com/api/Posts \
  -H "Content-Type: application/json" -d '{}'
HTTP/1.1 400 Bad Request

{"status":400,"error":"Bad Request","message":"Missing required field: title"}

Testing failure

DummyJSON and ReqRes both delay responses, and DummyJSON returns a status you pick. testingapis.com also has a real rate limiter that sends a 429 with Retry-After on the sixth request, a chaos group that fails a set number of times and then succeeds, and six pagination styles. The error responses guide has the details.

GET/api/todos/1?error=503

Which one to use

  • JSONPlaceholderif you're following a tutorial that uses it, or you want bigger lists. It has 5,000 photos and 500 comments, far more records than we keep.
  • DummyJSONif you want its products, users, posts and todos for a shop-style front end and don't need writes to stick.
  • ReqRes for a small user list and a quick demo. Its responses currently include a sponsor support object, so leave that out of exact-match assertions.
  • testingapis.com for saved writes, validation errors and failure testing, or when you also need GraphQL, WebSocket or SOAP from one host.

Moving from JSONPlaceholder takes two small changes, shown in the JSONPlaceholder alternative guide. If you use httpbin rather than a data API, see the httpbin route mapping.