Purpose
It's often necessary to carry out an action on a large number of accounts or user objects simultaneously. Many APIs only support a single object per transaction, and for several thousand transactions, this can take a very long time.
This group is gathering requirements for API calls that support bulk transactions that can change multiple user objects in a single transaction. These requirements will serve as input to the TIER API working group as well as material for the Provisioning Best Practices end product.
Use Cases for Bulk API Transactions
- On-boarding of batches of new students and other user types
- De-provisioning of graduated or separated students
- Provisioning large populations into a new service or target system.
- Data reconciliation between upstream and target systems
- Support for bulk-load tools such as for guest accounts for conferences
- Bulk credential locking as a result of phishing or compromised account
- Bulk change of entitlements or permissions due to a change in policy.