Skip to content
Switch branches/tags
Go to file


Failed to load latest commit information.
Latest commit message
Commit time

Verify Build Workflow

The apiman project (Open Source API Management)


This is the official Git repository for the apiman project:

The apiman project is a standalone API Management system that can be either run as a separate system or embedded within existing frameworks and platforms.

Get the code

The easiest way to get started with the code is to create your own fork of this repository, and then clone your fork:

$ git clone<you>/apiman.git
$ cd apiman
$ git remote add upstream git://

At any time, you can pull changes from the upstream and merge them onto your master:

$ git checkout master               # switches to the 'master' branch
$ git pull upstream master          # fetches all 'upstream' changes and merges 'upstream/master' onto your 'master' branch
$ git push origin                   # pushes all the updates to your fork, which should be in-sync with 'upstream'

The general idea is to keep your 'master' branch in-sync with the 'upstream/master'.

Building apiman


The following command compiles all the code, installs the JARs into your local Maven repository, and runs all of the unit tests:

$ mvn clean install

You can skip the test if you do not have docker installed:

$ mvn clean install	-DskipTests

Quickstart (i.e. How To Run It)

The project can be built and deployed on a variety of runtime platforms, but if you want to see it in action as quickly as possible try this:

$ mvn clean install -Pinstall-all-wildfly
$ cd tools/server-all/target/wildfly-dev-server
$ ./bin/

The above maven command will do the following:

  1. A full build of apiman
  2. Download WildFly 10.x
  3. Unpack and configure WildFly 10.x
  4. Deploy the WildFly 10.x version of apiman to WildFly

Once WildFly has started up, and if all went well, you can point your browser to the API Manager and log in (either register a new user or log in as the admin):

  • admin/admin123!

Note that this quickstart seeds a bunch of content into apiman. This is not strictly necessary, but it does populate the API Manager with some data so that it doesn't feel so lonely the first time you log in. You're welcome.

Contribute fixes and features

apiman is open source, and we welcome anybody who wants to participate and contribute!

If you want to fix a bug or make any changes, please log an issue in GitHub Issues describing the bug or new feature. Then we highly recommend making the changes on a topic branch named with the GitHub issue number. For example, this command creates a branch for the #317 issue:

$ git checkout -b apiman-317

After you're happy with your changes and a full build (with unit tests) runs successfully, commit your changes on your topic branch. Then it's time to check for and pull any recent changes that were made in the official repository:

$ git checkout master               # switches to the 'master' branch
$ git pull upstream master          # fetches all 'upstream' changes and merges 'upstream/master' onto your 'master' branch
$ git checkout apiman-317           # switches to your topic branch
$ git rebase master                 # reapplies your changes on top of the latest in master
                                      (i.e., the latest from master will be the new base for your changes)

If the pull grabbed a lot of changes, you should rerun your build to make sure your changes are still good. You can then either create patches (one file per commit, saved in ~/apiman-317) with

$ git format-patch -M -o ~/apiman-317 origin/master

and upload them to the JIRA issue, or you can push your topic branch and its changes into your public fork repository

$ git push origin apiman-317        # pushes your topic branch into your public fork of apiman

and generate a pull-request for your changes.

We prefer pull-requests, because we can review the proposed changes, comment on them, discuss them with you, and likely merge the changes right into the official repository.

Please try to create one commit per feature or fix, generally the easiest way to do this is via git squash. This makes reverting changes easier, and avoids needlessly polluting the repository history with checkpoint commits.

Code Formatting

When you are hacking on some apiman code, we'd really appreciate it if you followed the apiman coding standards. If you're using Eclipse, you can find a code formatter config file here:


You should be able to import that guy straight into Eclipse by going to Window->Preferences :: Java/Code Style/Formatter

Developer Portal

Apiman also comes with a developer portal. There you can allow developers to access your APIs. Developers can view and test your APIs to develop their own apps.
Check it out here: Apiman Developer-Portal

Looking for support?

Scheer PAS is the platform for flexible end-to-end support of individual processes. It stands for digitization and automation, regardless of how many people, systems or companies need to be integrated.

Scheer PAS API Management is based on Apiman and offers you also enterprise support.
You may visit Scheer PAS documentation for further details.