OAuth migration breaking changes

Feature	Old	New	Impact
Authentication Mechanism	Basic Authentication (username & password in headers)	OAuth 2.0 (token-based authentication)	Existing integrations must be updated to handle token generation and renewal.
Mandatory Request ID	Optional or not required	`RequestId` is mandatory in every request	All client applications must generate and include a unique Request ID per call.
HTTP Status Code Compliance	Custom or inconsistent status codes	Standard HTTP status codes (e.g., 200, 400, 401, 500)	Error handling logic in client apps may need to be revised.
Uniform Request/Response Structure	Varying formats across endpoints	Standardized JSON structure for all read/write APIs	Parsing logic and data models in client systems may need to be updated.
Enhanced Error Payload	Minimal or generic error messages	Detailed error structure with codes, messages, and hints	Clients should update error-handling routines to leverage new fields.
Endpoint URLs and Parameters	Legacy endpoint paths and parameter names	Updated endpoint paths and parameter naming conventions	All endpoint URLs and request payloads must be reviewed and updated.

Are there any breaking changes in the new endpoints besides authentication?