Modern businesses rely on a number of different types of software and systems to run a smooth operation. The success of these systems depends greatly on their ability to seamlessly communicate and exchange data with each other, so that they can help businesses efficiently solve problems. Processes need to flow easily and without friction, and enable everyone to stay in sync and informed. Application Programming Interface (API) is a software intermediary that makes it possible for applications to interact and communicate with each other in this manner.
APIs play an important role in many of the products and services we use today. For example, you use APIs when you check the weather, or use a social media application on your phone. The API connects the consumer asking for a service to the source or database.
The following analogy of a customer at a restaurant is a simple way of demonstrating how APIs work.
The customer sits at the table in a restaurant and has a choice of menu items to order from. The waiter takes the customer’s order and conveys it to the kitchen. The kitchen prepares the order and the waiter brings it to the customer.
The waiter in this scenario is the API, shielding the customer from the complicated processes of the kitchen, while still enabling the customer to interact with the kitchen and get the meal that they want. The organisation is the entity asking for the service, and is therefore the customer. The menu that the waiter hands to the customer in the restaurant is the documentation which explains what you can ask for from the API. The kitchen is the system that holds information and runs processes.
APIs can be grouped under the following categories:
Inbound APIs – From a Camms perspective, it is something which brings data into the Camms ecosystem from any number of potential source systems. While it is an incoming call to Camms which our inbound APIs need to ‘listen’ for, it is also an outbound call from the perspective of the external source system.
Outbound APIs – An outbound API therefore, allows you to take data out of the Camms ecosystem. Camms outbound APIs nee to ‘transmit’ this data so the external source system can pick it up as an incoming call.
Essentially, APIs help to get systems talking to each other. APIs connect otherwise disconnected systems such as ERPs, CRMs, finance, HR and marketing platforms and get them communicating with each other. You would want something happening in one system to automatically drive information into the other systems you use, without someone manually having to manage that process. And that is precisely what APIs do. They save time and money for the organisation overall, in terms of efficiency gains and improved experiences.
Camms.Connect provides your organisation with access to robust business services via standards-based, real-time APIs. These APIs provide opportunities for interaction with many critical areas of Camms, including staff, financials, projects, incidents, risks and measures. What Camms.Connect really does is provide the means for software to read information from inside Camms, input information from outside Camms and automatically react when things change.
There are many ways to use Camms.Connect APIs. Here are some:
The Camms.Connect APIs have been built with security in mind, and have all standard security measures in place. We use SSL communication tunnels and Camms API token to validate authority prior to data access.
In terms of usability, there is some level of technical expertise that is required to set up the APIs, especially if you are integrating with another system. But if you do not have that expertise in-house, Camms can provide that service for you.
If you are interested in learning more or would like to request a demo, please get in touch with us via firstname.lastname@example.org. You can also find out more details by visiting developer.cammsconnect.com.au.
Read about these updates in detail in last quarters Release Notes
and ready Release Note