As you probably know by now, we are in the process of migrating all of our customer’s accounts to our new dashboard and new account model. In the process of migrating our customers, access to add new accounts via the Platform API is now disabled. Here is some more information on how your reseller account will change with the migration:
The old JW Platform dashboard offered a multi-account environment we call our Reselling Model. In the new JW Player dashboard, we have updated this model in several ways:
We introduced the concepts of separate Users and Properties. This is more flexible versus the old sub-accounts, since users can now be assigned to one or more properties (content libraries).
We made available these multiple properties for all Enterprise customers. This means we don’t have separate reseller accounts anymore; everybody gets it.
We have removed the ability to whitelabel the dashboard through a custom logo, custom CSS and custom dashboard DNS mask, due to limited usage. Note that Contentserver DNS masking remains available.
When a reseller migrates to the new dashboard, all his sub-accounts will be automatically converted to properties. However, secondary user logins will not be transferred over and have to be re-created. Additionally, note that multiple properties are only available to Enterprise users, not Premium or Free.
We recommend migrating your account to our new dashboard by clicking the “Contact Us to Upgrade” button on your existing Account Dashboard. Once migrated, any new accounts that would normally be sub-accounts, can be added to your account as a new Property.
This is unacceptable! No one notified us of these changes to the API. This is going to affect our business model and affect our customers negatively. We have workflows that are written against the v1 API that are now broken. We should have been notified ahead of time, and given at least a sandbox environment to test against. I don't know what methodology for developing REST APIs you follow, but typically most companies version their REST APIs when making breaking changes (i.e. make a v2), so clients that have written against a specific API don't suddenly have their applications broken, and actually have time to migrate to the new version.
I apologize for the inconvenience. I was told that reseller accounts have been informed, but I am not directly involved with those notifications. I’m going to escalate your case to Meghan Carey, who is the sales person who recently handled your renewal. She should be able to get more information for you.
This question has received the maximum number of answers.