{ "error": { "message": "Invalid parameter", "type": "OAuthException", "code": 100, "error_subcode": 2388084, "is_transient": false, "error_user_title": "File type not supported", "error_user_msg": "The type of file is not supported.", "fbtrace_id": "AcCIxFILLMYV2ikmUMzqsd-" } }

I have encountered difficulties in sending messages via the API. Specifically, I am receiving the following error message:
Error Response: {"error":{"message":"(#135000) Generic user error","type":"OAuthException","code":135000,"error_data":{"messaging_product":"whatsapp","details":"Generic user error"},"fbtrace_id":"A1waaM6nHFNACvy0TmQySEo"}}
I have thoroughly reviewed our integration setup and confirmed that all parameters are correctly formatted and that our access token is valid. Additionally, we are adhering to WhatsApp's template policy, and our custom templates have been approved.
We were able to successfully send messages using the default template (Hello_world). However, we are unable to send any messages other than the default template.
I have mentioned the details bellow:
Business ID: 926486109278796 APP ID: 2139742859716726 WhatsApp account ID: 308550739016328
Despite our efforts to seek assistance through the Developer Community Forum, we have not received any response for the past 15 days. You can find the post detailing our issue here: Community Thread Link.
https://developers.facebook.com/community/threads/995496615293256/ https://developers.facebook.com/community/threads/838086257654372/ https://developers.facebook.com/community/threads/1033963401461816/
Additionally, I've observed that other users have reported a similar "Generic user error" (#135000) on the bugs page reference: Bug Report Link https://developers.facebook.com/support/bugs/355592997506030/ , where the Meta team successfully resolved the same issue. This leads me to believe that our error or the situation that we are in is also the same.
Upon reviewing these forums and bug reports, it appears that there might have been a misunderstanding or misclassification, as our WhatsApp Business Account might have been mistakenly flagged as engaging in spam activity. Please note that we are in the testing phase internally at Ernst & Young LLP and have not used this for production purposes.
I assume that you have flagged our account as spam by mistake, so i kindly request you to consider removing or lifting the restriction of our account.
Therefore, we kindly request the Meta team to review and lift any restrictions that might have been placed on our account in error. This restriction is significantly impacting our operations, and we urgently need to resolve this issue.

when i create a whatsApp business API app i always get Onboarding Failure You have been temporarily blocked from performing this action.

We are building a platform for WhatsApp business messaging. For this, we need to test the product catalog messaging APIs.

However, it seems there is no way to do so without creating a public business account and adding a payment method.

Is there a means to access the APIs without going through the above steps? Especially the payment method as we do not wish to start paying for testing our product before going live.

We have created a product catalog and connected it to the WhatsApp business account on an actual phone number. But we cannot send messages without adding a payment method.

So when i create or edit my WhatsApp templates trough meta web portal, it seems that there is kind a problem with call to action buttons and dynamic URL.
My dynamic URL looks like:
https://www.my-website.com.co/payment?reference={{1}}
Where {{1}} is a alphanumeric value, for example:
https://www.my-website.com.co/payment?reference=12345678
But for some reason, when i submit the template, a slash is added between my URL and the dynamic value, so after the revision is confirmed, if go back and edit again the tempate, the slash is added:
https://www.my-website.com.co/payment?reference=/{{1}}
When I use the template to send an message, obviously the button is not working because URL is not well formed:
https://www.my-website.com.co/payment?reference=/12345678
Thing is that this was working fine some weeks ago as I was able to create templates with no slash automatically added, but now is completely broken, there is no way to change it.
I am going to try editing it trough API call, but do not thinks it going to help me.
Attached to this ticket you can find a screenshot for better understanding.
Will appreciate any help in case I am doing something wrong.
Regards. Max B