The updateUser() and createUser() methods always perform two API requests under the hood: (1) the create/update request, and (2) a subsequent getUser() request.

In latency-sensitive applications where the result of getUser() is not required, this means an extra un-needed sequential round-trip network request. This fact is not apparent from the API or documentation.

Proposal

Add a second, optional parameter to createUser() and updateUser() called something like noFetchUserRecord which defaults to false (existing behaviour). If true, the getUser() request will be skipped, and the function will return Promise<void>, avoiding the un-needed round-trip request.