🔐 Token Endpoint Enhancement – JSON Support Added & Stricter Validation Enforced

Release Date: April 16, 2025

What’s New?
The /token authentication endpoint now supports requests with Content-Type: application/json, in addition to the existing application/x-www-form-urlencoded support.

This change applies to:

POST /api/authentication/{tenant_id}/token

Why?
Supporting JSON-formatted requests improves developer experience by aligning with modern integration standards. It allows clients to choose the format that best fits their architecture and ensures consistency across API calls.

⚠️
Important: The /api/authentication/{tenant_id}/token endpoint now enforces stricter content-type validation.
Only application/json and application/x-www-form-urlencoded are supported. Requests using other formats will return a 415 Unsupported Media Type error.

⚠️Important: The /api/authentication/{tenant_id}/token endpoint now enforces stricter content-type validation. Only application/json and application/x-www-form-urlencoded are supported. Requests using other formats will return a 415 Unsupported Media Type error.

⚠️
Important: The `/api/authentication/{tenant_id}/token` endpoint now enforces stricter content-type validation.
Only `application/json` and `application/x-www-form-urlencoded` are supported. Requests using other formats will return a 415 Unsupported Media Type error.