Provisioning Endpoints (2022/06)
7 min
the provisioning resources allow users to setup players or change player setups base url for this endpoint https //api bsn cloud/2022/06/rest/provisioning post /setups/tokens/ issues a token which allows you to register players in the current network required scope token bsn api main devices setups token create request body a token info entity docid\ rmbcir76z7ojsyjb u2pp request example the example request parameters and headers are set as follows post /2022/06/rest/provisioning/setups/tokens/ http/1 1 host api bsn cloud connection keep alive authorization bearer {{useraccesstoken}} accept application/json, application/vnd bsn error+json accept encoding gzip,deflate there is no request body since the required information is passed in the url success response \<font color="#089a4d">200\</font> a setup token has been issued for players on the specified network example { "token" {{token}}, "scope" "cert", "validfrom" "2024 05 21t00 00 00z", "validto" "2024 11 17t00 00 00z" } failure response \<font color="#9a0808">300\</font> the requested representation could not be returned because it is ambiguous (there are multiple requested representations) \<font color="#9a0808">400\</font> either the request or request body is malformed and therefore invalid \<font color="#9a0808">401\</font> the access token is invalid or not specified \<font color="#9a0808">403\</font> the supplied access token, though valid, doesn't provide access to this method \<font color="#9a0808">406\</font> the server cannot return the data representation that you requested (as specified in the "accept" header) \<font color="#9a0808">5xx\</font> any 500 code is an internal server error get /setups/tokens/{token}/ validates a player setup token on the current network and retrieves its metadata required scope token bsn api main devices setups token validate segment token \<font color="#704ae0">string \</font> an oauth2 token for player registration in the current network request example the example request parameters and headers are set as follows token is set to {{token}} get /2022/06/rest/provisioning/setups/tokens/{{token}}/ http/1 1 host api bsn cloud connection keep alive authorization bearer {{useraccesstoken}} accept application/json, application/vnd bsn error+json accept encoding gzip,deflate success response \<font color="#089a4d">200\</font> returns a token info entity docid\ rmbcir76z7ojsyjb u2pp example { "token" {{token}}, "scope" "cert", "validfrom" "2024 05 16t16 36 04 000z", "validto" "2026 05 16t16 36 04 000z" } failure response \<font color="#9a0808">300\</font> the requested representation could not be returned because it is ambiguous (there are multiple requested representations) \<font color="#9a0808">400\</font> the request is malformed and therefore invalid \<font color="#9a0808">401\</font> the access token is invalid or not specified \<font color="#9a0808">403\</font> the supplied access token, though valid, doesn't provide access to this method \<font color="#9a0808">404\</font> the server cannot find the requested resource (the token is expired or invalid) \<font color="#9a0808">406\</font> the server cannot return the data representation that you requested (as specified in the "accept" header) \<font color="#9a0808">5xx\</font> any 500 code is an internal server error delete /setups/tokens/{token}/ revokes a player setup token on the current network required scope token bsn api main devices setups token revoke segment token \<font color="#704ae0">string \</font> an oauth2 token for player registration in the current network request example the example request parameters and headers are set as follows token is set to {{token}} delete /2022/06/rest/provisioning/setups/tokens/{{token}}/ http/1 1 host api bsn cloud connection keep alive authorization bearer {{useraccesstoken}} accept application/json, application/vnd bsn error+json accept encoding gzip,deflate success response body \<font color="#089a4d">204\</font> the player setup token has been revoked failure response \<font color="#9a0808">300\</font> the requested representation could not be returned because it is ambiguous (there are multiple requested representations) \<font color="#9a0808">400\</font> the request is malformed and therefore invalid \<font color="#9a0808">401\</font> the access token is invalid or not specified \<font color="#9a0808">403\</font> the supplied access token, though valid, doesn't provide access to this method \<font color="#9a0808">404\</font> the server cannot find the requested resource (the token is expired or invalid) \<font color="#9a0808">406\</font> the server cannot return the data representation that you requested (as specified in the "accept" header) \<font color="#9a0808">500\</font> any 500 code is an internal server error