I confirm that the payload's field name is not consistent with the one returned in the API's body.

However, please consider that MantisBT APIs (both SOAP and REST) have been using name instead of username in this context since release 1.1.0a4 (2007), and I don't think such inconsistency is worth breaking backwards-compatibility.

Maybe @vboctor will care to comment.

For it to be username was obvious to me (I started with API creating user) but if it will break backwards-compatibility you can use name - just to be consistent.

Looks like we use name when returning issues and logged in user. So the create operation is what is not consistent. username makes sense, but name is used for other entities like statuses, versions, view_states, categories, etc.

Hence, I suggest the fix would be that user create accepts both name and username. If both are specified, then use name.

That's ok with me ;-)

PR: https://github.com/mantisbt/mantisbt/pull/1506