BrightSign Network Web API Reference Manual v.3.8 - Manual (Page 16)

4
Specific Update Methods: e.g. UpdateGroupsAutorun
These methods receive Entity IDs and one or more values for updating logically related properties within that entity
(for example, changing the minimum required firmware values for a group). Methods of this type don’t require the
client to retrieve the object first. This may be useful for small dialogs, groups of controls (such as those in
BrightAuthor), or internal client logic for sealing off certain parts of functionality from end users.
Object Permissions
Currently, all supported entities have a predetermined set of Object Permissions that cannot be changed. Customizable
permissions will be implemented in the future.
SOAP Endpoints
Currently, the BrightSign Network Web API consists of two web services with nearly identical configurations: the
Application Service and the Content Upload Service. Each web service has two SOAP endpoints: One is configured to
use the WS-* specification and the other to use the WS-I Basic Profile.
WS-*
The WS-* endpoint is intended for rich, multifunctional server or desktop applications that support features such as
sessions and transactions. The endpoint also supports its own rich security module and complex messaging format.
It would be difficult and time consuming to manually implement the required functionality for WS-*, including message
serialization/de-serialization, encoding/decoding, connection management, and state management. Therefore, in order to
utilize this endpoint, you will first need find a library that can create a service reference (i.e. proxy class) for your language
and/or platform. Windows features built-in tools for creating service references for .NET applications, where the WS-*
specification is the default web service endpoint configuration. Official or third-party tools/libraries have also been built for
some, but not all, languages and platforms.