Getting error while testing Custom API Request (Beta) option.

Hello,
I need help to identify why Custom API Request (Beta) of Whatsapp Cloud API is returning the error message below:

(#100) The parameter messaging_product is required.

I need to send a message template of the "location_request_message" type, but I'm facing this difficulty.
That message template does not require Meta approval, so there is no way to send it in the conventional way, using "Send Template Message (Beta)".

For further instructions, check the Meta tutorial in the link below:
https://developers.facebook.com/docs/whatsapp/cloud-api/guides/send-messages/location-request-messages/

Workflow: (it is on the first route - option “Motorista não recusou") https://connect.pabbly.com/workflow/share/AUkENgNUUDNfFQFrVAsHIAwYAgYHXlU2UUhWRAYJVi5bAQZtBURdNw5CBCYDVFMyXxZUPlUKUDALHwcDUAYCcVBJBQdcX10nWxZTKAJbCzgBXwQsA2I#

Hi @Carlos Melo,

There was an unnecessary quotation mark at the end of your JSON. We removed it, and it seems to have fixed the issue.

Thank you, Arshil.
Yeah, it seems the message is sent.
However, the phone number doesn't receive the message. I tried two different.
They are phone numbers that receive messages from workflows normally.

So, how can we solve that ?

The endpoint appears to have been set up correctly as per Meta's API documentation. Could you please try executing the same endpoint in Postman and see if you receive the message? Also, try using a different phone number

Ok,
I ran the same endpoint in Postman and got the same result: message sent successfully, but the target number did not receive the message.
In this case I tried a third phone number that I have.

See below what Postman returned:

200OK
{
"messaging_product": "whatsapp",
"contacts": [
{
"input": "+5527992978257",
"wa_id": "5527992978257"
}
],
"messages": [
{
"id": "wamid.HBgNNTUyNzk5Mjk3ODI1NxUCABEYEjZDREI4NDAzNzc2REYxMUIxNgA="
}
]
}

So we can interpret that as a problem originating from Meta, and there is not much we can do.
Right?
:cautious:

Hello @Carlos Melo,

Yes, the issue is originating from Meta, as you have also verified using Postman. We recommend reaching out to Meta's support team regarding this issue for further assistance.