# JSON Server [![Node.js CI](https://github.com/typicode/json-server/actions/workflows/node.js.yml/badge.svg?branch=master)](https://github.com/typicode/json-server/actions/workflows/node.js.yml) Get a full fake REST API with __zero coding__ in __less than 30 seconds__ (seriously) Created with <3 for front-end developers who need a quick back-end for prototyping and mocking. * [Egghead.io free video tutorial - Creating demo APIs with json-server](https://egghead.io/lessons/nodejs-creating-demo-apis-with-json-server) * [JSONPlaceholder - Live running version](https://jsonplaceholder.typicode.com) * [__My JSON Server__ - no installation required, use your own data](https://my-json-server.typicode.com) See also: * :dog: [husky - Git hooks made easy](https://github.com/typicode/husky) * :owl: [lowdb - local JSON database](https://github.com/typicode/lowdb) * β [xv - a beautifully simple and capable test runner](https://github.com/typicode/xv)
[Become a sponsor and have your company logo here](https://github.com/users/typicode/sponsorship) ## Sponsor __Please help me build OSS__ π [GitHub Sponsors](https://github.com/sponsors/typicode) :heart: ## Table of contents - [Getting started](#getting-started) - [Routes](#routes) * [Plural routes](#plural-routes) * [Singular routes](#singular-routes) * [Filter](#filter) * [Paginate](#paginate) * [Sort](#sort) * [Slice](#slice) * [Operators](#operators) * [Full-text search](#full-text-search) * [Relationships](#relationships) * [Database](#database) * [Homepage](#homepage) - [Extras](#extras) * [Static file server](#static-file-server) * [Alternative port](#alternative-port) * [Access from anywhere](#access-from-anywhere) * [Remote schema](#remote-schema) * [Generate random data](#generate-random-data) * [HTTPS](#https) * [Add custom routes](#add-custom-routes) * [Add middlewares](#add-middlewares) * [CLI usage](#cli-usage) * [Module](#module) + [Simple example](#simple-example) + [Custom routes example](#custom-routes-example) + [Access control example](#access-control-example) + [Custom output example](#custom-output-example) + [Rewriter example](#rewriter-example) + [Mounting JSON Server on another endpoint example](#mounting-json-server-on-another-endpoint-example) + [API](#api) * [Deployment](#deployment) - [Links](#links) * [Video](#video) * [Articles](#articles) * [Third-party tools](#third-party-tools) - [License](#license) ## Getting started Install JSON Server ``` npm install -g json-server ``` Create a `db.json` file with some data ```json { "posts": [ { "id": 1, "title": "json-server", "author": "typicode" } ], "comments": [ { "id": 1, "body": "some comment", "postId": 1 } ], "profile": { "name": "typicode" } } ``` Start JSON Server ```bash json-server --watch db.json ``` Now if you go to [http://localhost:3000/posts/1](http://localhost:3000/posts/1), you'll get ```json { "id": 1, "title": "json-server", "author": "typicode" } ``` Also when doing requests, it's good to know that: - If you make POST, PUT, PATCH or DELETE requests, changes will be automatically and safely saved to `db.json` using [lowdb](https://github.com/typicode/lowdb). - Your request body JSON should be object enclosed, just like the GET output. (for example `{"name": "Foobar"}`) - Id values are not mutable. Any `id` value in the body of your PUT or PATCH request will be ignored. Only a value set in a POST request will be respected, but only if not already taken. - A POST, PUT or PATCH request should include a `Content-Type: application/json` header to use the JSON in the request body. Otherwise it will return a 2XX status code, but without changes being made to the data. ## Routes Based on the previous `db.json` file, here are all the default routes. You can also add [other routes](#add-custom-routes) using `--routes`. ### Plural routes ``` GET /posts GET /posts/1 POST /posts PUT /posts/1 PATCH /posts/1 DELETE /posts/1 ``` ### Singular routes ``` GET /profile POST /profile PUT /profile PATCH /profile ``` ### Filter Use `.` to access deep properties ``` GET /posts?title=json-server&author=typicode GET /posts?id=1&id=2 GET /comments?author.name=typicode ``` ### Paginate Use `_page` and optionally `_limit` to paginate returned data. In the `Link` header you'll get `first`, `prev`, `next` and `last` links. ``` GET /posts?_page=7 GET /posts?_page=7&_limit=20 ``` _10 items are returned by default_ ### Sort Add `_sort` and `_order` (ascending order by default) ``` GET /posts?_sort=views&_order=asc GET /posts/1/comments?_sort=votes&_order=asc ``` For multiple fields, use the following format: ``` GET /posts?_sort=user,views&_order=desc,asc ``` ### Slice Add `_start` and `_end` or `_limit` (an `X-Total-Count` header is included in the response) ``` GET /posts?_start=20&_end=30 GET /posts/1/comments?_start=20&_end=30 GET /posts/1/comments?_start=20&_limit=10 ``` _Works exactly as [Array.slice](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Array/slice) (i.e. `_start` is inclusive and `_end` exclusive)_ ### Operators Add `_gte` or `_lte` for getting a range ``` GET /posts?views_gte=10&views_lte=20 ``` Add `_ne` to exclude a value ``` GET /posts?id_ne=1 ``` Add `_like` to filter (RegExp supported) ``` GET /posts?title_like=server ``` ### Full-text search Add `q` ``` GET /posts?q=internet ``` ### Relationships To include children resources, add `_embed` ``` GET /posts?_embed=comments GET /posts/1?_embed=comments ``` To include parent resource, add `_expand` ``` GET /comments?_expand=post GET /comments/1?_expand=post ``` To get or create nested resources (by default one level, [add custom routes](#add-custom-routes) for more) ``` GET /posts/1/comments POST /posts/1/comments ``` ### Database ``` GET /db ``` ### Homepage Returns default index file or serves `./public` directory ``` GET / ``` ## Extras ### Static file server You can use JSON Server to serve your HTML, JS and CSS, simply create a `./public` directory or use `--static` to set a different static files directory. ```bash mkdir public echo 'hello world' > public/index.html json-server db.json ``` ```bash json-server db.json --static ./some-other-dir ``` ### Alternative port You can start JSON Server on other ports with the `--port` flag: ```bash $ json-server --watch db.json --port 3004 ``` ### Access from anywhere You can access your fake API from anywhere using CORS and JSONP. ### Remote schema You can load remote schemas. ```bash $ json-server http://example.com/file.json $ json-server http://jsonplaceholder.typicode.com/db ``` ### Generate random data Using JS instead of a JSON file, you can create data programmatically. ```javascript // index.js module.exports = () => { const data = { users: [] } // Create 1000 users for (let i = 0; i < 1000; i++) { data.users.push({ id: i, name: `user${i}` }) } return data } ``` ```bash $ json-server index.js ``` __Tip__ use modules like [Faker](https://github.com/faker-js/faker), [Casual](https://github.com/boo1ean/casual), [Chance](https://github.com/victorquinn/chancejs) or [JSON Schema Faker](https://github.com/json-schema-faker/json-schema-faker). ### HTTPS There are many ways to set up SSL in development. One simple way is to use [hotel](https://github.com/typicode/hotel). ### Add custom routes Create a `routes.json` file. Pay attention to start every route with `/`. ```json { "/api/*": "/$1", "/:resource/:id/show": "/:resource/:id", "/posts/:category": "/posts?category=:category", "/articles?id=:id": "/posts/:id" } ``` Start JSON Server with `--routes` option. ```bash json-server db.json --routes routes.json ``` Now you can access resources using additional routes. ```sh /api/posts # β /posts /api/posts/1 # β /posts/1 /posts/1/show # β /posts/1 /posts/javascript # β /posts?category=javascript /articles?id=1 # β /posts/1 ``` ### Add middlewares You can add your middlewares from the CLI using `--middlewares` option: ```js // hello.js module.exports = (req, res, next) => { res.header('X-Hello', 'World') next() } ``` ```bash json-server db.json --middlewares ./hello.js json-server db.json --middlewares ./first.js ./second.js ``` ### CLI usage ``` json-server [options]