Document Okta API type coercion

[exitcode0]

Thank you for getting involved with Okta's Developer Docs!

Affected page(s):

• https://developer.okta.com/docs/reference/core-okta-api/
• https://developer.okta.com/docs/api/

Describe the problem(s):

If a user omits or provides incorrect data to the Okta API The Okta API will either fall back to defaults or it will attempt to perform type coercion I think some of the former is documented, but I believe the latter is undocumented?

If possible, describe a proposed fix:

It would be good to have documentation around how Type Coercion works in the Okta API I'd imagine if this is performed by Okta's API gateway this should be consistent for all Okta APIs

[brianduffield-okta]

Hi @exitcode0 I'll create an internal ticket to track this request. Thanks for the post.