The current asynchronous batch datum delete API is good for deleting large time-based ranges of datum, but another use case to support is deleting a set of specific datum, identified uniquely, irrespective of time. This has come up where applications want to remove the odd invalid datum, and the only way to accomplish that currently is to submit batch delete jobs for each datum using a very narrow date range.

It might be most conventient if the new API were synchronous. It could enforce a maximum number of identifiers per request, to limit the overall impact of each operation.