Nighttime Pachinko Marathon


    0.9.0 • Public • Published


    Circle CI Coverage Status Dependency Status devDependency Status

    API Description SDK

    Wardaddy: Best job I ever had.

    Fury provides uniform interface to API description formats such as API Blueprint.



    Fury.js is available as npm module.

    Install globally:

    $ npm install -g fury

    or as a dependency:

    $ npm install --save fury

    Refract Interface

    Fury.js offers an interface based on the Refract Project element specification and makes use of the API description and data structure namespaces. Adapters convert from formats such as API Blueprint into Refract elements and Fury.js exposes these with API-related convenience functionality. For example:

    import fury from 'fury';
    const source = '# My API\n...';
    fury.parse({source}, function(err, api, warnings) {

    Once you have a parsed API it is easy to traverse:

    api.resourceGroups.forEach(function (resourceGroup) {
      resourceGroup.resources.forEach(function (resource) {
        resource.transitions.forEach(function (transition) {
          transition.transactions.forEach(function (transaction) {
            const request = transaction.request;
            const response = transaction.response;
            console.log(`${request.method} ${request.href}`);
            console.log(`${response.statusCode} (${response.header('Content-Type')})`);

    It is also possible to do complex document-wide searching and filtering. For example, to print out a listing of HTTP methods and paths for all defined example requests:

     * Prints out something like:
     * POST /frobs
     * GET /frobs
     * GET /frobs/{id}
     * PUT /frobs/{id}
     * DELETE /frobs/{id}
    function filterFunc(item){
      if (item.element === 'httpRequest' && item.statusCode === 200) {
        return true;
      return false;
    console.log('All API request URIs:');
    api.find(filterFunc).forEach(function (request) {
      console.log(`${request.method} ${request.href}`)

    Multiple Fury Instances

    There may come a day when you need to have multiple Fury instances with different adapters or other options set up in the same program. This is possible via the Fury class:

    import {Fury} from 'fury';
    const fury1 = new Fury();
    const fury2 = new Fury();

    Writing an Adapter

    Adapters convert from an input format such as API Blueprint into refract elements. This allows a single, consistent interface to be used to interact with multiple input API description formats. Writing your own adapter allows you to add support for new input formats.

    Adapters are made up of a name, a list of media types, and three public functions: detect, parse, and an optional serialize. A simple example might look like this:

    export const name = 'my-adapter';
    export const mediaTypes = ['text/'];
    export function detect(source) {
      // If no media type is know, then we fall back to auto-detection. Here you
      // can check the source and see if you think you can parse it.
      return source.match(/some-test/i) !== null;
    export function parse({minim, generateSourceMap, source}, done) {
      // Here you convert the source into refract elements. Use the `minim`
      // variable to access refract element classes.
      const Resource = minim.getElementByClass('resource');
      // ...
      done(null, elements);
    export function serialize({api, minim}, done) {
      // Here you convert `api` from javascript element objects to the serialized
      // source format.
      // ...
      done(null, outputString);
    export default {name, mediaTypes, detect, parse, serialize};

    Now you can register your adapter with Fury.js:

    import fury from 'fury';
    import myAdapter from './my-adapter';
    // Register my custom adapter
    // Now parse my custom input format!
    fury.parse({source: 'some-test\n...'}, function (err, api) {

    Legacy Interface

    This is the older "legacy" interface for API Blueprint and Apiary Blueprint parsing.

    API Blueprint Parsing

    var parser = require('fury').legacyBlueprintParser;
    var source = '# My API\n';
    parser.parse({ code: source }, function(error, api, warnings) {

    Markdown Rendering

    The legacy interface also offers access to Markdown rendered as used internally by API and Apiary Blueprint parsers.

    var markdownRenderer = require('fury').legacyMarkdownRenderer;
    var source = '# My API\n';
    markdownRenderer.toHtml(source, {}, function(error, html) {


    Building & Testing

    Parts of Fury.js are written in Coffeescript, so you must build the final library before it can be used. All of the build/test/etc commands are run through npm:

    # Build the library 
    npm run compile
    # Run the unit and integration tests 
    npm test
    # Generate a coverage report 
    npm run coverage
    # Open the HTML report 
    open coverage/lcov-report/index.html




    npm i fury-experimental

    DownloadsWeekly Downloads






    Last publish


    • pksunkara
    • smizell
    • kylef
    • apiary-sre