Skip to main content
Skip table of contents

Applying an account profile to an existing account

Request

Sometimes, the CRM may need to apply an account profile to accounts that already exist in OpenTV Video Platform. This may be necessary, for example, if you have asked NAGRA to create a new account profile for a specific group of accounts and you need to update those accounts to use the new profile.

To apply an account profile to an account, the CRM should send a PUT request to:

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

In deployments that use NAGRA'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 NAGRA.

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

If you do not supply a value for a parameter that already has a value, it will be set to null.

So the recommended approach is to use a GET <endpoint> request to get the <entity>, change <what you need to change>, then use this modified set of parameters in the body of the PUT request.


  • uid – the unique account ID (in URL), which is returned when you create an account
  • accountProfile – the ID of the account profile to be applied to the account

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

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

See also

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

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.