Improve OpenAPI response schemas by marking guaranteed properties as required

[CatLover01]

The OpenAPI specification appears to be missing required declarations for many response properties.

For example, properties that appear to be consistently returned by the API are not included in the schema's required arrays. This causes OpenAPI-generated clients and TypeScript types to treat these properties as optional, even though they appear to be guaranteed in actual API responses.

Could the response schemas be reviewed and have properties marked as required where they are guaranteed to be present?

This would make the OpenAPI specification more accurately reflect the actual API contract and would improve the quality of generated clients.

One related question: OAuth is currently represented through the securitySchemes definitions, with the authorization and token URLs hosted at https://secure.soundcloud.com rather than the API host. Is the intention that the OAuth endpoints themselves are intentionally excluded from the OpenAPI paths, since they belong to the separate secure.soundcloud.com service?

[dpreussler]

For the related question: Is the intention that the OAuth endpoints themselves are intentionally excluded from the OpenAPI paths,
since they belong to the separate secure.soundcloud.com service?

Exactly.
But i'll discuss with the team if we can publish a schema for those calls to