Wix’s Account APIs are intended to support large-scale businesses that create, design, and/or manage large numbers of Wix sites. These APIs enable businesses to manage access to their associated sites.
When someone registers to *.wix.com, both a new user ID and account ID are created for them. User IDs are specific to a single person, and aren’t shared, while account IDs can be shared between multiple users. The owner of an account can invite users to access and manage some or all of the account’s sites and other assets, such as domains, custom templates, sites, and premium planset. The users of a specific account are known as team members.
Team members have access at the account level, but can be limited to access and manage only one specific site within the account.
Accounts are particularly useful when a business employs multiple staff members who should all have access and permissions to manage one or more sites created for the business, and when a design company creates and maintains ownership of sites for clients. In these cases, creating a team and sharing account access with the relevant users allows the right people to edit the relevant sites to get their work done and keep sites and businesses running smoothly.
When someone becomes a team member in an account, they can be given access to account-level (domains, payment and billing info, etc.) and site-level data.
Account owners can use roles to limit team members’ access to various tasks and or interfaces of the account. For example, an account owner can block a team member's access to specific sites, or to add features that require payment. See Managing Your Team for more information.
An account can have many sites created directly within the account, which are created and managed in the account workspace.
In addition, an account can become a parent account to other accounts. For example, a parent company might want to align their branding across the websites for all their branches, and/or maintain management access to their child accounts' assets.
Parent accounts can provide access to private apps and assets (media, etc.) to all their child accounts, while hiding any sensitive assets, and can pass on the parent account’s custom branding. Parent accounts can also use API keys to make API calls affecting sites in their child accounts.