Skip to content
Node.js validator used to confirm adherance of a FinSpec document to the puslibhed schema. (See for documentation)
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

The FinSpec Specification Validator

The FinSpec validator is a tool designed to validate that FinSpec JSON documents correctly match the specification as defined here, or to return error messages indicating where the validation is failing.


  1. Install Node JS and NPM. If you do not have installed these already, grab them from here.

  2. You will also need curl. If this isn't installed by default on your operating system, it can be downloaded from here..

  3. Git clone the repo (or download / unpack the zip).

  4. Launch a terminal, cd into the install folder and download the node packages with npm install.

  5. Pat yourself on the back.

Validating FinSpec Documents

  1. Launch terminal and go to the installation folder. Run the validator server using command:

    node server.js
  2. Keep this sever running in background or foreground to be able to perform the validations.

  3. Your schema can now be validated by using curl like this:

curl -XPOST localhost:9999/validate?version=<schema_version> -F json=@/path/to/finspec.json

Where, schema_version is target FinSpec schema version.


Version 2.1 (Current Version):

curl -XPOST localhost:9999/validate?version=2.1 -F json=@./myschema-2.1.json
{"pass":true,"message":"Good job!"}

Version 2.0 (prior version):

curl -XPOST localhost:9999/validate?version=2.0 -F json=@./myschema-2.0.json
{"pass":true,"message":"Good job!"}

NOTE This validator is only supporting versions 1.x and 2.x of the schema. All 0.x versions are no longer supported. Please contact FixSpec at for assistance upgrading from an older schema version.

Changing port

By default, the node application uses port 9999. If you prefer a different port, simple shut the server down, edit server.cfg and restart.

You can’t perform that action at this time.