Updating recording settings

Request

If you create a new recording profile, you will need to apply it to a set of accounts.

To do this, for each account to which the new NPVR profile is to be applied, the CRM should send a PUT request to:

https://<host>:<port>/adm/v1/accounts/preHashedPassword/{uid}

In deployments that use NAGRAVISION's Security Services Platform (SSP), this request must be made twice – once to OPF, and once to SSP.

The URLs of the two endpoints will be provided to you by NAGRAVISION.

Headers

• x-correlation-id – identifier for logging, to correlate messages across a call flow

• Authorization – bearer token obtained in Getting an access token

• nv-tenant-id – the tenant ID

• Content-Type: application/json

Mandatory arguments

• uid – the unique account ID (in URL), which is returned when you create an account

• npvrProfileName – the recording (NPVR) profile to be applied to the account
  
  

  

  pvrStatus must also be set to ENABLED on the account for NPVR to be available to the user.

Other arguments

See PUT /v1/accounts/preHashedPassword/{uid } in the Account and Device Manager (ADM) API documentation.

Response

A successful request returns an HTTP 200 status.

A bad request returns an HTTP 400 status.

If the token is invalid, an HTTP 403 status is returned

If the tenant or account does not exist, the request returns an HTTP 404 status.

Example

{
  "matchedCount": 1,
  "modifiedCount": 1
}

See also

For full details of this API, see the Account and Device Manager (ADM) API documentation.