Okta has a json representation of objects such as 'users', json schema interchanged on API...

Okta has a json representation of objects such as 'users', json schema interchanged on API calls, as an example, but what about the format of information regarding of a user going to a SCIM server for creating the user in an On Premises application?

Solution: Format stays the same: json