Developer Help Center

Upgrading Accounts

Use the upgrade resource to change attributes of accounts created with the signup resource.

POST /partner/account/upgrade

Table 1. Request Body Parameters

Parameter

Type

Description

partnerAPIKey

Mandatory

string

API key provided by your Revelator account manager.

enterpriseId

Mandatory

integer

The Revelator account ID for the child account you want to upgrade. This ID was returned in the signup request which created the account.

newType

Optional

string

The type of child account. By default, this value will not be updated for the account.

  • Growth is the recommended account type for all API customers.

Note that changing the account type has no impact on existing rights holders; the initial rights holder that was created with the signup request will not be impacted in anyway, and no additional rights holder will be created with this request.

newMaxArtists

Optional

integer

Maximum number of artists the user can create in the account. By default, this value will not be updated for the account. The following count as an artist towards the maximum:

  • Each artist named as the artist for a release (for at least one release)

  • Each compilation release (there is no artist named for the release; there are artists named for each track)

newStoreAccess

Optional

object

Controls which digital service providers (DSPs) the child account can distribute to. By default, this value will not be updated for the account.

Parameter

Type

Description

type

string

  • all - All stores available in the partner's parent account will be available

  • some - The stores specified in storeIds will be available

  • none - The child account will not be able to distribute releases

storeIds

array of integers

The Revelator ID for each store that will be available. Only specify DSPs which are enabled in your parent account.

Lookup DSP IDs using the GET /common/lookup/stores resource. Provide an access token to retrieve only the DSPs enabled for a specific account.



Table 2. Response

Response Body

None

HTTP codes

Code

Description

204 No Content

Success

403 Forbidden

If the request would grant an account access to resources the partner doesn't have access to. For example, setting storeIds to a store the partner doesn't have access to.

409 Conflict

If the request would prevent an account from using resources it's already using. For example, setting newMaxArtists to 1 for an account that has 5 artists.