The actual proxy part of ApiAxle.
A free, locally hosted API management solution. A proxy for your api, statistics for your api & a powerful api of its own.
There are three components which make up the Api Axle system:
$ npm install apiaxle-proxy
This is the aspect of the system which does the actual proxying. It sits in front of your API and does the authentication, key checking, queries per day/second checking. This is the bit you want if you want anything. More detail on the main site.
$ npm install apiaxle-api
This is the (optional) API for managing users, keys and endpoints. Once installed, run it with:
$ npm install apiaxle-repl
A way to administer your ApiAxle installation via a command line. Once installed, run it with:
You then get a prompt where you can type
help to find out more.
This is a set of libraries which is required for the above components.
Check the main site for more detailed installation instructions.
This repository is auto-built and published as mapzen/apiaxle.
This project uses two
Dockerfiles, one for production usage named
and a second for development of ApiAxle itself, named
Docker Compose is configured to build the development version for you, see
below for examples.
Environment variables can be used to configure
DEBUG_MODE. Below are defaults for production:
^(.+?)\\.api\\.(extra backslash required for JSON)
docker-compose up -d redisdocker-compose up -d apidocker-compose up -d proxy
docker-compose run repl
docker-compose run repl test
docker-compose run --entrypoint sh repl
api acme create endPoint='localhost:8000'key 1234 createapi acme linkkey 1234
curl localhost:3000?api_key=1234 -H 'Host: acme.api.localhost'