One of the handy features of using is having that single source of truth for your application. It’s modeled in one place so everyone on the team can always get the current version. With the API, this includes your CI/CD process as well. The app now provides you with the necessary steps and data to use the API.  Just hit the download menu in the modeler, or an app’s hamburger menu in the catalog, and select the “API Download Information” link.



You’ll get a description of where to retrieve all the pertinent data and the format of an example CURL command:

curl -H 'Authorization: token <github personal access token>' \
-H 'x-yipeeio-context:<context id>' \<type of download>/<application id>

“Type of download” refers to our currently supported orchestrators:

  • compose
  • composeV3
  • kubernetes
  • kubernetebundle (a compressed tar file)
  • openshift
  • openshiftbundle (a compressed tar file)

To save you some time, at the bottom of the dialog is the CURL command already mostly assembled with the IDs for your context and the selected application. You just need to fill in a personal access token from your GitHub account and the type of download. Here’s an example of a completed command:


curl -H 'Authorization: token 1d5934336ca76731baca23422e7049de19894345' \
-H 'x-yipeeio-context: d38ccf84-5b57-11e7-8362-8738d8f31731' \


Once assembled, you can use that CURL command in your CI/CD system to retrieve your chosen orchestration file and send your build process off to the races with the most up to date version of your app. The team uses this very process today to build the application (which is of course modeled in Yipee). We are working on a Jenkins plugin which will simplify integration with Jenkins jobs. If this would be valuable to you, please drop us a note at allows you to create, collaborate and now more conveniently orchestrate your microservices application. Sign up for today to start collaborating (it’s free!).