Difference between revisions of "API"
(Created page with "=== Emersion API Infrastructure === Emersion has an integration layer designed to enable our clients to connect their applications into some of our business layer functionali...") |
|||
| Line 1: | Line 1: | ||
=== Emersion API Infrastructure === | === Emersion API Infrastructure === | ||
| − | Emersion has an | + | Emersion has implemented an External API Framework Layer to assist in clients integrating directly into parts of the Emersion Eco-System. |
| + | |||
| + | Most additions to the framework to date have been directly from client requests, and Emersion is able to extend or add new functionality on a case by case and quoted basis. | ||
| + | |||
| + | For a quote on a solution to fit your requirement, please contact the Emersion Sales team. | ||
| + | |||
| + | For an individual or business looking to work with our API layer, we can recommend the freeware software Soap UI to perform testing and gain guidance on operations contained within the API. | ||
| + | |||
| + | This software allows you to view the methods contained within the API and send and receive test calls to the API without having to write a system. | ||
| + | |||
| + | === Security Layer === | ||
| + | To integrate with Emersion’s API Framework, clients will need to implement a SOAP Client, utilising SSL certificate as security. The SSL certificates are provided by Emersion, and may be subject to a professional services charge | ||
| + | depending on your Emersion agreement. | ||
| + | |||
| + | The WSDL for each set of functions is documented in the next section. | ||
| + | |||
| + | For production, use; https://external.emersion.com.au/ | ||
| + | |||
| + | For testing, use; https://external-prerelease.emersion.com.au/ | ||
| + | |||
| + | NOTE: Please contact Emersion before you begin testing on Pre-Release to ensure the environment is stable and not using any test code | ||
| + | |||
| + | === API Documentation === | ||
There are different API types, listed below; | There are different API types, listed below; | ||
Revision as of 09:17, 24 October 2014
Emersion API Infrastructure
Emersion has implemented an External API Framework Layer to assist in clients integrating directly into parts of the Emersion Eco-System.
Most additions to the framework to date have been directly from client requests, and Emersion is able to extend or add new functionality on a case by case and quoted basis.
For a quote on a solution to fit your requirement, please contact the Emersion Sales team.
For an individual or business looking to work with our API layer, we can recommend the freeware software Soap UI to perform testing and gain guidance on operations contained within the API.
This software allows you to view the methods contained within the API and send and receive test calls to the API without having to write a system.
Security Layer
To integrate with Emersion’s API Framework, clients will need to implement a SOAP Client, utilising SSL certificate as security. The SSL certificates are provided by Emersion, and may be subject to a professional services charge depending on your Emersion agreement.
The WSDL for each set of functions is documented in the next section.
For production, use; https://external.emersion.com.au/
For testing, use; https://external-prerelease.emersion.com.au/
NOTE: Please contact Emersion before you begin testing on Pre-Release to ensure the environment is stable and not using any test code
API Documentation
There are different API types, listed below;
Minimal - Basic Introductory Methods
Services - Mostly Service Centric Based Methods (most methods go here.)
Retail Services - User Based Information including Payment Integration
