flaky
Real-looking data at real URLs, with the same resource shapes as JSONPlaceholder. The difference is that the caller decides how it behaves: _delay, _status…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Real-looking data at real URLs, with the same resource shapes as JSONPlaceholder. The difference is that the caller decides how it behaves: _delay, _status and _fail_rate work on every endpoint, so a slow or broken backend is a query parameter rather than a local mock server.
Out-of-range values are rejected with a 400 rather than ignored — a tool for testing failures should not fail quietly itself.
Endpoints 64
users
- GETList users
/users10 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a users record (echoed, not stored)
/usersReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one users record
/users/:id - PUTReplace a users record (echoed, not stored)
/users/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a users record (echoed, not stored)
/users/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a users record (echoed, not stored)
/users/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - GETList the posts belonging to a users
/users/:id/postsMatches on posts.userId. - POSTCreate one of a users's posts (echoed, not stored)
/users/:id/postsposts.userId is taken from the path, whatever the body says. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that… - GETList the albums belonging to a users
/users/:id/albumsMatches on albums.userId. - POSTCreate one of a users's albums (echoed, not stored)
/users/:id/albumsalbums.userId is taken from the path, whatever the body says. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that… - GETList the todos belonging to a users
/users/:id/todosMatches on todos.userId. - POSTCreate one of a users's todos (echoed, not stored)
/users/:id/todostodos.userId is taken from the path, whatever the body says. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that…
posts
- GETList posts
/posts100 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a posts record (echoed, not stored)
/postsReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one posts record
/posts/:id - PUTReplace a posts record (echoed, not stored)
/posts/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a posts record (echoed, not stored)
/posts/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a posts record (echoed, not stored)
/posts/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - GETList the comments belonging to a posts
/posts/:id/commentsMatches on comments.postId. - POSTCreate one of a posts's comments (echoed, not stored)
/posts/:id/commentscomments.postId is taken from the path, whatever the body says. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that…
comments
- GETList comments
/comments500 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a comments record (echoed, not stored)
/commentsReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one comments record
/comments/:id - PUTReplace a comments record (echoed, not stored)
/comments/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a comments record (echoed, not stored)
/comments/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a comments record (echoed, not stored)
/comments/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick.
albums
- GETList albums
/albums100 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a albums record (echoed, not stored)
/albumsReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one albums record
/albums/:id - PUTReplace a albums record (echoed, not stored)
/albums/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a albums record (echoed, not stored)
/albums/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a albums record (echoed, not stored)
/albums/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - GETList the photos belonging to a albums
/albums/:id/photosMatches on photos.albumId. - POSTCreate one of a albums's photos (echoed, not stored)
/albums/:id/photosphotos.albumId is taken from the path, whatever the body says. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that…
photos
- GETList photos
/photos1000 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a photos record (echoed, not stored)
/photosReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one photos record
/photos/:id - PUTReplace a photos record (echoed, not stored)
/photos/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a photos record (echoed, not stored)
/photos/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a photos record (echoed, not stored)
/photos/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick.
todos
- GETList todos
/todos200 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a todos record (echoed, not stored)
/todosReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one todos record
/todos/:id - PUTReplace a todos record (echoed, not stored)
/todos/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a todos record (echoed, not stored)
/todos/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a todos record (echoed, not stored)
/todos/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick.
products
- GETList products
/products100 records. Any field can also be used as a filter, e.g. ?userId=3. - POSTCreate a products record (echoed, not stored)
/productsReturns the record with an id, exactly as JSONPlaceholder does, and does not persist it. The response carries x-mock-write to say so. Use a sandbox for writes… - GETGet one products record
/products/:id - PUTReplace a products record (echoed, not stored)
/products/:idReturns your body as the whole record, keeping the id. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - DELETEDelete a products record (echoed, not stored)
/products/:idEchoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick. - PATCHChange fields on a products record (echoed, not stored)
/products/:idReturns the record with your fields merged in. Echoed, not stored: the response carries x-mock-write to say so. Use a sandbox for writes that stick.
sandbox
- POSTCreate a sandbox where writes persist
/sandboxNeeds a key. Lives 24 hours. Writes inside it are stored; everything outside is read-only. - GETList records in a sandbox
/sandbox/:sandboxId/:resource - POSTCreate a record that persists
/sandbox/:sandboxId/:resource
custom
- POSTCreate a mock server from your own JSON
/customSend an array, or an object whose values are arrays; each array becomes an endpoint. No account needed. Lives for ?days= days, 1 to 9 (default 1), then is… - POSTCreate a mock of your own API from its OpenAPI spec
/custom/openapiSend an OpenAPI 3 or Swagger 2.0 document as JSON. Each GET list endpoint, and its /{id} route, becomes a resource with ten generated records shaped by the… - GETRead one of your own resources
/custom/:id/:resourceFiltering, sorting, paging, _select and every chaos parameter apply here exactly as they do to the built-in resources. - GETDownload it as files that run locally
/custom/:id/exportnode, python, java and csharp each return a complete single-file server with your data embedded — no install, no network, and the chaos parameters work…
scenario
- POSTCreate a failure sequence, in either direction
/scenario_fail_rate is random and cannot be asserted on; _status never changes. A scenario is a counter, which is what retry logic and circuit breakers actually need —… - GETHow far through the sequence you are
/scenario/:id - POSTRewind the counter without spending an attempt
/scenario/:id/resetFor a test's beforeEach. The inline ?_scenario_reset=1 rewinds too, but that request then becomes attempt 1.
account
- POSTIssue a free API key
/keysNo confirmation email; the key is returned immediately. Asking again with the same address returns the key you already have rather than minting another. - GETMachine-readable description of the API
/metaResource names, row counts, tier limits, and which tier you are on.
API details
- Base URL
https://flakyapi.dev/v1- Authentication
- A bearer token in the Authorization header
- Operations
- 64 operations on 30 pathsGET 24POST 19PUT 7PATCH 7DELETE 7
- Main resources
- users 12albums 8posts 8comments 6photos 6products 6todos 6custom 4sandbox 3scenario 3
- Response formats
application/json- Description format
- OpenAPI 3.1.0, API version
1.0.0 - Links
- OpenAPI document · Support
- Listed from
- Flakyapi's published OpenAPI description
How to test the flaky in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the flaky collection, without the publisher's secrets.
- Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “List users” (GET /users), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the flaky?
Real-looking data at real URLs, with the same resource shapes as JSONPlaceholder. The difference is that the caller decides how it behaves: _delay, _status… It is listed under Developer tools and has 64 endpoints.
Who publishes the flaky?
It is listed from Flaky API's public API description (an OpenAPI document), not published by Flaky API on Swastik Codes. Anyone who controls flakyapi.dev can claim the profile by adding a DNS TXT record.
What is the base URL of the flaky?
Requests go to https://flakyapi.dev/v1. Endpoint paths are added to this base URL.
How do I authenticate with the flaky?
With A bearer token in the Authorization header.
How many endpoints does the flaky have?
64 operations on 30 paths (24 GET, 19 POST, 7 PUT, 7 PATCH, 7 DELETE). The largest groups are users, albums, posts, comments.
Is forking the flaky free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.