The BrightSign Network REST API exposes a large set of BSN functionality using a standardized architecture of REST endpoints. Developers can use these endpoints to build web applications for creating presentations and playlists, managing devices, monitoring device health, uploading files, and more.
URLs and Endpoints
...
Endpoints are appended to this base URL. Except for the /token
endpoint, all BSN endpoints accept trailing slashes (e.g. /presentations/
).
Headers
Accept
All data retrieval requests REST calls should contain the "Accept" header. The server supports values of All endpoints support the "application/json" and "application/xml" . types–except for the /sessions/
endpoint, which uses a unique set of content types for file uploads.
Note | ||
---|---|---|
| ||
This The BrightSign REST API manual documentation describes request/response entities using JSON examples and data types (integer, string, array, etc.). |
...
All update/create requests should contain the "Content-Type" header. The server supports values of All endpoints support the "application/json" and "application/xml" types–except for the /sessions/
endpoint, which uses a unique set of content types for file uploads.
Authorization
All requests, except for those to the /token
endpoint, must contain the "Authorization" header. See the Authentication page for more details.