How are Admin API Keys Scoped?

Admin API keys can be scoped at the Environment level.  A few notes:

• You can still create a global Admin API key.
• All Admin API keys are subject to approvals that are set on an Environment.  If you have approvals required in an Environment, changes made via the API will need to be approved as defined in that Environment.
• All Admin API keys can add splits and segments and make changes in Environments with editing permissions set, similar to Administrators
• When you create a split or a segment you first create a 'meta' object.  A meta-split or meta-segment is not associated with any specific Environment.  As a result, there is no restriction on adding, deleting, or getting information about a meta-split or meta-segment across Environments and Workspaces.  However, unless you have a key for an Environment you cannot add rules to a split or IDs to a segment for that Environment.  If a split or segment has a definition in an Environment, you cannot delete it unless you have a key for that Environment.