Thank you for sharing this information. It does not have an impact on our server-side validation.

Hi Kirlos, as you can see from the response's message field, there are two elements (id and name) underneath, you need to append .id to specify the first search field for id, so change the "message.from" to "messsge.from.id" should solve this problem.

You may write a pre-hook cloud code script with your validating logic and integrate it with [TurnShieldOn()](https://getbraincloud.com/apidocs/apiref/?cloudcode#capi-matchmaking-turnshieldon) method.

How about passing the slug as a parameter along with the webhook URL? This will allow your script to parse the parameter and perform actions accordingly.

You can hook the script to brainCloud authentication API and check the loginCount from the response, the related doc can be found here.