Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
GET /v1/registry/
Returns the entire registry dump. The hidden registry sections are not returned in this response.
Request Example
The example request parameters and headers are set as follows:
Code Block |
---|
GET /api/v1/registry/ HTTP/1.1 Host: {{player_ip_address}} Accept: application/json |
Response Body
success
bool: If the operation is successfulvalue
object: The keys are the names of the registry sections. These are some examples:brightscript
string: The BrightScript key-value pairsnetworking
string: The networking key-value pairs
GET /v1/registry/:section/:key/
Returns a particular key value for a specified section and key.
Segment Values
section
string: The name of the registry sectionkey
string: The name of the registry key
Request Example
The example request parameters and headers are set as follows:
section
is set tohtml
key
is set touse-brightsign-media-player
Code Block |
---|
GET /api/v1/registry/html/use-brightsign-media-player/ HTTP/1.1 Host: {{player_ip_address}} Accept: application/json, application/vnd.bsn.error+json |
PUT /v1/registry/:section/:key/
Creates registry values. Do a GET first to see which keys are available.
Note |
---|
Applications rely on the values they have set in the registry. Please be mindful of what you type to avoid putting the player in an unstable state. |
Segment Values
section
string: The name of the registry section (for example, "html" or "networking")key
string: The name of the registry key
Request Example
The example request parameters and headers are set as follows:
section
is set tohtml
key
is set touse-brightsign-media-player
Code Block |
---|
PUT /api/v1/registry/html/use-brightsign-media-player/ HTTP/1.1 Host: {{local_ip_address}} Accept: application/json Content-Type: application/json Content-Length: 33 |
This is the example request body:
Code Block | ||
---|---|---|
| ||
{ "value": "0" } |
DELETE /v1/registry/:section/:key/
Remove the specified registry values.
Note |
---|
Applications rely on the values they have set in the registry. Please be mindful of what you type to avoid putting the player in an unstable state. |
Segment Values
section
string: The name of the registry section (for example, "html" or "networking")key
string: The name of the registry key
Request Example
The example request parameters and headers are set as follows:
section
is set tohtml
key
is set touse-brightsign-media-player
Code Block |
---|
DELETE /api/v1/registry/html/use-brightsign-media-player/ HTTP/1.1 Host: {{player_ip_address}} Accept: application/json |
DELETE /v1/registry/:section/
Deletes an entire registry section
Request Example
The example request parameters and headers are set as follows:
section
is set totest_section
Code Block |
---|
DELETE /api/v1/registry/test_section/ HTTP/1.1 Host: {{player_ip_address}} Accept: application/json |
GET /v1/registry/recovery_url/
Retrieves the recovery URL stored in the player registry
Request Example
recovery_url
is the recovery URL in the player registry
Code Block |
---|
GET /api/v1/registry/recovery_url/ HTTP/1.1 Host: {{player_ip_address}} Accept: application/json |
Response Body
success
bool: A flag indicating whether the request was successfully readvalue
string: The recovery URL
PUT /v1/registry/recovery_url/
Updates the recovery URL in the player’s registry.
Request Body
url
string: The value of the recovery URL
Request Example
The example request parameters and headers are set as follows:
url
is set towww.google.com
Code Block |
---|
PUT /api/v1/registry/recovery_url/ HTTP/1.1
Host: {{player_ip_address}}
Authorization: Bearer {{UserAccessToken}}
Accept: application/json
Content-Type: application/json
Content-Length: 37 |
Request Body
Code Block | ||
---|---|---|
| ||
{ "url": "www.google.com" } |
Endpoints:
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|