HTTP AAA to a SMS TXT Service with Token Insert

rivet!

It looks like you did everything right. Here are a few things you can check to make sure everything is working correctly:

Make sure the URL you use to post your post is correct.
Make sure the custom body contains the correct information. Specifically, ensure that the To header contains the correct mobile number and the Body header contains the correct OTP code.
Verify that the TokenCall custom header value is correct.
Verify that the client's Content-Type header has the correct value.
If you have checked all these things and still are not receiving any TXT, then the problem may be on the TokenCall provider side. In this case, you should contact them for further assistance.

In addition, I also recommend additional configuration Two-Factor Authentication Methods to protect against scammers and hackers. 2FA adds an extra layer of security to your account as hackers not only need to know your password, but also have access to your mobile device in order to gain access to your account.

Here are some tips for setting up 2FA:

Use a reliable 2FA provider such as Google Authenticator or Authy.
Enable 2FA for all important accounts, including email, bank accounts, social media, and any other accounts where you have access to sensitive information.
Do not store 2FA codes in the public domain.

Hope this information helps!