Title: WPML & Error code”: 422, “message”: “Unauthorized
Last modified: April 13, 2025

---

# WPML & Error code”: 422, “message”: “Unauthorized

 *  Resolved [kizotux](https://wordpress.org/support/users/kizotux/)
 * (@kizotux)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/wpml-error-code-422-message-unauthorized/)
 *     ```wp-block-code
       Hello,I encountered a problem and then I found a solution that could help other users. In the combination of WPML & Elementor Form & FluentSMTP and Outlook or Office 365 connection, sending emails from the web form only works on the original domain and language, if the other languages ​​are in the directories. If you try to send a request via the web form in other languages, you will get an error:"code": 422,"message": "Unauthorized","errors": ["Unauthorized"The solution to the problem is to add paths for each language in the Microsoft Entra admin center:Home > Enerprise application > All applications > FluentSMTP domain.com | Properties > App registrations > FluentSMTP domain.comUnder "Authentication" Web - Redirect URLs, you should add the other languages ​​in addition to the basic domain in the main language. For example:https://domain.com/wp-json/fluent-smtp/outlook_callback (main language - original record)https://domain.com/it/wp-json/fluent-smtp/outlook_callback (Italian language)https://domain.com/de/wp-json/fluent-smtp/outlook_callback (German language)etc...for all languages ​​used on the site.I assume that the same problem occurs with all WP plugins for sending emails through forms that do not solve the path change for callback URLs themselves.Best regards
       ```
   

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [aurelofou](https://wordpress.org/support/users/aurelofou/)
 * (@aurelofou)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/wpml-error-code-422-message-unauthorized/#post-18415212)
 * finally it is working !!!
   thank you
 *  Plugin Support [Ibrahim Sharif](https://wordpress.org/support/users/ibrahimsharif/)
 * (@ibrahimsharif)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/wpml-error-code-422-message-unauthorized/#post-18427905)
 * Hello [@kizotux](https://wordpress.org/support/users/kizotux/),
 * Thank you so much for sharing your solution so thoroughly. This information will
   undoubtedly assist other users facing the same problem with multi-language setups.
   We really appreciate you taking the time to document and share your findings.
 * It’s a valuable insight that these callback URLs often need manual configuration
   for different languages, and we’ll definitely keep this in mind for future documentation
   and potential plugin improvements.
 * Thanks again for your contribution to the FluentSMTP community!
 *  Thread Starter [kizotux](https://wordpress.org/support/users/kizotux/)
 * (@kizotux)
 * [1 year, 1 month ago](https://wordpress.org/support/topic/wpml-error-code-422-message-unauthorized/#post-18430970)
 * Hello [@ibrahimsharif](https://wordpress.org/support/users/ibrahimsharif/),
 * I’m glad if the information helps someone.
 * Kind regards

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘WPML & Error code”: 422, “message”: “Unauthorized’ is closed to new replies.

 * ![](https://ps.w.org/fluent-smtp/assets/icon.svg?rev=2458343)
 * [FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider](https://wordpress.org/plugins/fluent-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-smtp/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [kizotux](https://wordpress.org/support/users/kizotux/)
 * Last activity: [1 year, 1 month ago](https://wordpress.org/support/topic/wpml-error-code-422-message-unauthorized/#post-18430970)
 * Status: resolved