Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Node server for dynamic, fake JSON.


Node server for dynamic, fake JSON.

npm install -g dyson

Check out some demo services.

Build Status npm package dependencies npm version


Dyson allows you to define JSON endpoints based on a simple template object:


When developing client-side applications, for data usually either static JSON files are used, or an actual server, backend, datastore, API, you name it. Sometimes static files are too static, and sometimes an actual server is not available, not accessible, or too tedious to setup.

This is where dyson comes in. Get a full fake server for your application up and running in minutes.


  • Easy configuration, extensive options
  • Dynamic responses
    • Responses can use request data (e.g. to simulate different login scenarios based on username):
      • Request path
      • GET/POST parameters
      • Cookies
    • Respond with different status code for specific requests (e.g. 404 for ?id=999)
    • Includes random data generators
  • Supports to proxy non-configured endpoints to actual services
  • Supports GET, POST, PUT, DELETE (and OPTIONS)
  • Supports CORS
  • Includes dummy image generator
    • Use any external or local image service (included)
    • Supports base64 encoded image strings
  • Supports required parameter validation

Endpoint Configuration

Configure endpoints using simple objects:

    path: '/user/:id',
    template: {
        id: function(params, query, body) {
        address: {
            zip: g.zipUS,

The path string is the usual argument provided to Express, as in app.get(path, callback);.

The template object may contain properties of the following types:

  • function: the function will be invoked with arguments (params, query, body, cookies)
  • string, boolean, number, array: returned as-is
  • object: will be recursively iterated
  • promise: if the function is a promise, it will be replaced with the resolving value

Note: the template can also be a function returning the actual data. The template function itself is also invoked with arguments (params, query, body, cookies).


In addition to configured endpoints, dyson registers a dummy image service at /image. E.g. requesting /image/300x200 serves an image with given dimensions.

This service is a proxy to Dynamic Dummy Image Generator by Russell Heimlich.


The default values for the configuration objects:

    cache: true,
    size: function() {
        return _.random(2,10);
    collection: false,
    callback: response.generate,
    render: response.render
  • cache:true means that multiple requests to the same path will result in the same response
  • size:function is the number of objects in the collection
  • collection:true will return a collection
  • callback:function
    • the provided default function is doing the hard work (but can be overridden)
    • used as middleware in Express
    • must set res.body and call next() to render response
  • render:function
    • the default function to render the response (basically res.send(200, res.body);)
    • used as middleware in Express

Fake data generators

You can use anything to generate data. Here are some suggestions:

Just install the generator(s) in your project to use them in your templates:

npm install dyson-generators --save-dev

Please refer to the project pages for usage and examples (here's one using dyson-generators).


Containers can help if you need to send along some meta data, or wrap the response data in a specific way. Just use the container object, and return the data where you want it. Functions in the container object are invoked with arguments (params, query, data):

    path: '/users',
    template: user.template,
    container: {
        meta: function(params, query, data) {
            userCount: data.length
        data: {
            all: [],
            the: {
                way: {
                    here: function(params, query, data) {
                        return data;

And an example response:

    "meta": {
        "userCount": 2
    data: {
        all: [],
        the: {
            way: {
                here: [
                        "id": 412,
                        "name": "John"
                        "id": 218,
                        "name": "Olivia"

Combined requests

Basic support for "combined" requests is available, by means of a comma separated path fragment.

For example, a request to /user/5,13 will result in an array of the responses from /user/5 and /user/13.

The , delimiter can be configured (or disabled).

Status codes

By default, all responses are sent with a status code 200 (and the Content-Type: application/json header).

This can be completely overridden with the status property, e.g.:

    path: '/feature/:foo?',
    status: function(req, res) {
        if( === '999') {
            res.send(404, 'Feature not found');

Would result in a 404 when requesting /feature/999.


npm install -g dyson

Note: You need to install dyson as a global module, but configuration files are local to your project.


In any project you can generate some dummy templates to get started:

dyson init [dir]

This script copies dummy config files to [dir]/get/, [dir]/post/, [dir]/put/, and [dir]/delete/. These folders are scanned for configuration files when dyson is started:

dyson [dir]

This starts the services configured in [dir] at localhost:3000.

You can also provide an alternative port number by just adding it as a second argument (e.g. dyson path/ 8181).


For a demo project, see webpro/dyson-demo. This demo is also running at nodejitsu.

Project Configuration

Optionally, you can put a dyson.json file next to the configuration folders (inside [dir]). It enables to configure some behavior of dyson:

    "multiRequest": ",",
    "proxy": true,
    "proxyHost": "",
    "proxyPort": 8080
  • Setting multiRequest to false disables the combined requests feature.
  • By default, the proxy is set to false

Development & run tests

git clone
cd dyson
npm install
npm test

Articles about dyson



Something went wrong with that request. Please try again.