Plugins architecture offers 3rd party developpers the possibility to develop connectors to their specific system, called from various hooks in S-360.
The 3rd party developer must implement an API transmitted by S-360, following S-360 rules of plugin implementation.
Then the plugin can be submitted to S-360 for approval and deployed in an planned S-360 release.
Plugins can leverage different elements for S-360:
|Firehose contact||Each time a contact is created/updated, the plugin is called|
|Firehose order||Each time an order is closed, the plugin is called|
|Tariff eligibility verification||To check if the validity of a tariff from an external system|
|External Manager||Used to generate tickets and handle tickets from external ticketing providers|
|Payment Integration||To integrate payments received from a bank and release reservations|
|Access control||Called by S-360 to push tickets towards an external access control system and retrieve the controlled tickets|
|External Printing||Used to push tickets to external printer and handle their printing feedback|
|Firehose Product||Each time a product is created/updated the plugin is called|
|Loyalty||to push and retrieve loyalty points from a loyalty point provider|
|Sender||To send messages - SMS, emails - to contacts defined in SAM|
|Url shortener||To shorten urls to be sent in messages|
|Data Export||To extract data executing queries|