Feature Request: Support for `Authorization: Bearer <API_KEY>` Header

[jov-one]

Hi Team,

I’m reaching out with a feature request for the transactional email API (POST /v3/smtp/email).

Currently, the API expects the API key to be passed in a custom header like this:

api-key: xkeysib-<your_key>

Many platforms and services expect authorization to be passed using the standard HTTP header:

Authorization: Bearer <xkeysib-<your_key>

Would you consider supporting this standard format as an alternative method for authenticating API requests? It would make integration with many systems more seamless and secure.

Thank you for your consideration!