Feature request: Accept API token via Authorization header

warning I did use ai to write this because I don’t have a tech background

Hi, I’m trying to connect Dynalist to Muse through a secure credential manager, and I’ve hit an authentication blocker.

The issue: Dynalist’s API only accepts the API token in the JSON POST body. But the credential manager I’m using (like many integration platforms) can only inject secrets into HTTP headers, query parameters, or URL path segments — it cannot place a secret inside a JSON request body. The two are fundamentally incompatible.

I’ve verified the API itself works perfectly — a direct call with the token in the body succeeds. It’s purely the credential delivery mechanism that’s the problem.

Would you consider also accepting the token via an Authorization header (e.g. Authorization: Token <api_key> or Bearer)? This is standard REST API practice and would unlock Dynalist for a wide range of integrations and automation platforms that currently can’t authenticate.