For future reference: there is no need for a separate request subclass in this case.  This is because the boolean flag applies to all account creation scenarios.

Having two separate request classes usually makes better sense when the object created can be one of two (or more types) or when some request options only apply to one type and other request options only apply to another type: you typically want to restrict any options specific to a type to their own request class (and then use the Visitor pattern to distinguish between them).

In the interest of time, I'll adjust the implementation and commit it to the pull request.