The AAF 6.2 product contains an SMS TOTP method preconfigured for MessageBird. Which is great.

However, the method uses the "OLD HTTP-API_v1" as MessageBird refers to it and is dated somewhere in 2014.
This method forces one to use a usename/password setup.
The new and current MessageBird API (v2) uses an API key for authenticating.

To keep the adoption level low, i'd recommend to add an additional method to AAF for MessageBird which uses an API key.