Objective
This document is meant to show the different reasons to choose either the API (https://wiki.openmrs.org/display/docs/API) or web services (https://wiki.openmrs.org/display/docs/Web+Services)
API
For the API the external application installs the API jar in their application and could connect to a single OpenMRS database if they had the proper credentials in their runtime properties file
Benefits
- The API has more calls than web services and in general will be prioritized for development over the web services
Disadvantages
- The external application can only connect to one OpenMRS instance
- The external application must be able to run the API jar file
Web Services
For an external application to get or put data into an OpenMRS instance via web services, you have to install the rest module (https://wiki.openmrs.org/display/docs/Webservices.rest+Module) in the OpenMRS instances and then program the application to make the appropriate calls in json format over REST to the web services module.
Benefits
- Can make calls to different OpenMRS instances easily
- Can be used by any application without having to install