Subowners

The Subowners API allows you to create and manage limited-use login credentials for accessing your account. Subowners provide controlled access to specific features, such as slicing content, without exposing full account credentials. Permissions can be assigned per subowner to restrict their actions within your system.

Subowners are not full-fledged accounts. For example, content sliced and encoded by one of your subowners is still owned by you and you have full control over it. Subowners are more like additional doors into parts of your account - you create the doors and the keys but never have to give out the master key (your main account credentials).

In our system, a subowner is a limited-use account login attached to your account. By using the subowner integration APIs, you can create additional login credentials for accessing your account, and you can assign different levels of permissions to those credentials. For example, the slicer, which is used for preparing assets, requires a user name and an API key. You may need to allow some people in your organization to slice content but do not wish to give them access to call APIs. With the subowner APIs, you can create a separate user name / API key for them and grant them just enough permission to slice content.

Unlike normal accounts, the user name for a subowner must not be an email address. Instead, a convention is used that consists of a short prefix for your account, followed by a dot, followed by a single word user name. For example, "ptvn.dsmith" and "ptvn.jdoe" might be two subowners created for a particular account. The system does not enforce the convention, but it may in the future. Currently the prefixes are not registered with the system, so you are free to choose any prefix you want.

---

Permissions

---

Endpoints

---