A Service can subscribe to Notifications to be notified of data changes made within the platform.
All requests between a Service and the platform are signed for security reasons. See Signing requests.
All requests to 3rd party service are backend-to-backend and signed with Service access token. Access token is created Service deployment time, stored in both service and the platform, and not communicated between them (pre-shared).
signable_content is a concatenation of the following:
Resource path (including leading slash, e.g. ”/path/to/script”)
Query string (including leading question mark, e.g. ”?attr=value”)
salt is a random string, it should change from request to request and be sufficiently random.
Salt and generated signature are sent in HTTP headers:
Receiving end calculates signature from the access_token stored locally and data from the request and checks if it matches the one in the request. Any request failing signature check must return 403 forbidden.
To add a Service to a platform's instance, super admin is to provide three parameters:
Raise a support ticket to organise new Service setup tasks
timerelease allows to set a lock on assets, like images uploaded for a media element, so that even if the client application knew the url to the asset, the user would not be able to view it until a specific point in time.
An application specifies which service(s) it needs. When a project is created, the platform enables all required Services automatically.
The platform sends a Project handshake request to the Service in the following cases:
A new service has been added to the project
Service config in the app is changed
Project name is changed
Tabs are entries in Studio main menu.
Tabs are fetched by sending a request to the service when a project or an event is selected in Studio:
An icon that is shown for the service tab on Studio main menu.
Can be any Font Awesome 5.14 icon that support fal prefix including pro icons.
To specify an icon the tabs response must contain icon field with name of the desired icon.
By default Studio use th icon.
The notifications mechanism is deprecated and will be removed soon. Use webhook events instead when possible.
The purpose is to allow a Service to use Studio as Event/Element management system, where some processing is done by the Service. To enable this Studio notifies the service whenever data changes are made in Studio. When notified the Service then fetches up-to-date data from the platform using feeds or Control API.
Please note that notification does not guarantee that any of the data was actually changed after the previous notification, or that the current state of the object is final and complete. So service should track changes by itself.
There can be a lag of a couple of seconds between a change and notification.
On success service needs to respond with 200 and empty body.
On error service needs to respond with corresponding status and empty body.
This API allows adding a tab with Service analytics data to the Event's analytics page. The platform enables this feature according to corresponding flag in instance handshake response. The platform makes Analytics request to the Service to get it's data.
Field data source
Service can act as a data source for a custom field, providing dynamic content.
Service can provide assets which LViS passes to the App. The platform fetches assets from the service by calling Assets.
Each service can provide service-specific data feeds. These feeds will be requested from the service and uploaded to the public CDN by the platform. Feeds list is configured during instance handshake in the handshake response.
Event feeds are uploaded periodically while event is running. The platform fetches Service specific Event data feed by calling Event-level feed.
Uploaded public feed will be listed on the Event feeds page, and available at the following URL:
//<static_host>/events/<first two chars of event uuid>/<event uuid>/<service_type>/<feed_id>.json
Subscribing to webhook events is a way to integrate with the platform and perform actions in response to changes, without the need for periodic API pooling.