abi2oas

abi2oas

Ingests a smart contract's ABI and autogenerates a JSON conforming to the OpenAPI Spec, ready for Swagger Codegen.

Usage

CLI

Install globally via npm, yarn, or your preferred Javascript package manager:

npm install -g abi2oas

yarn global add abi2oas

Use in your terminal of choice by running:

abi2oas <path_to_contract.json> <path_to_output.json> [options]

The CLI options let you specify values from the config file -- you can learn by running abi2oas --help. If you are on Windows, you might need to refresh your path by restarting the terminal.

Node.js

You can also use abi2oas directly within node. Install directly to your project:

npm install --save abi2oas

// OR

yarn add abi2oas

Import like any other package, then use the convert method to build the OpenAPI object:

const abi2oas = require('abi2oas');

const contractApiSpec = abi2oas.convert(<path_to_contract.json>, <output_path.json>, [config]);

.convert() runs synchronously and returns the serialized object corresponding to the OpenAPI JSON, along with saving the JSON to the specified path. config in this method may either be an object or a string pointing to a config JSON. Read below for config spec.

Method Mapping

The smart contract is mapped to the OpenAPI spec on a per-function basis:

• Each function's name becomes an API path (e.g. whitelistAddress function yields /whitelistAddress path). If the function is constant, then its path accepts GET requests. Otherwise, it accepts POST requests.
• A tag is automatically generated for each function, representing its dynamic scope (e.g. a whitelistAddressScope tag). All methods for each function automatically have its tag, along with any other custom tags specified in the config.
• Definitions are automatically generated for each function-method's params and response (e.g. whitelistAddress_post_params & whitelistAddress_post_params_response), as well as definitions for receipts and basic types.

Config

The config JSON lets you configure Swagger and Web3 options for your API. All keys are optional, the values shown are used by default.

{
  "version": "1.0.0",
  "schemes": ["https"],
  "host": "localhost:8080",
  "basePath": "/",
  "tags": [ // Optional custom tags...],
  "api": { // Optional, add tags to methods; see below }
}

Custom Tags

You can specify additional tags using the tags key.

{ ...,
  "tags" : [
    {
      "name": "admin",
      "description": "Only admin access"
    },
  ...]
}

Custom tags can be attached per-endpoint and per-method using the api key. For instance, if you wanted to tag the POST method for contract function "whitelistAddress" with "admin", for instance, your config file would include:

{ ...,
  "tags" : { // above }
  "api" : {
    "whitelistAddress" : {
      "post" : {
        "tags" : ["admin"]
      }
    }
  }
}

Development

You can find our roadmap on GitHub.

Licensing

abi2oas is developed & maintained by Eximchain, released for public use under the Apache-2.0 License.

Output from abi2oas is configured by default to use the same license.