Urgent: Error #135000 with WhatsApp Meta API
1

We've been facing a persistent issue with the WhatsApp Meta API for the past week. Specifically, while messages using default templates send successfully, those using our custom templates consistently encounter "Error #135000: Generic user error."

Despite our thorough verification of all configurations and methods, this issue persists exclusively with custom templates.

Vivek
Asked about 6 months ago
Selected Answer
1

only the default template is working; the rest show a generic user error. This seems to be a Meta issue, and it hasn’t been resolved. I raised a complaint with direct support, but they said it’s a technical issue and directed me to the developer community. Unfortunately, no one has been able to solve the error there. It’s very complicated to deal with.

August 3 at 1:35 AM
Vivek
1

Looks like it is an issue from meta and specifically for numbers added recently, i have an existing meta business account with phone number added way before 6 months and its working without any problem, but when i added new number last month then this error started to appear. then i removed recently added number and my app with old number worked without any instance of this error.

So i thought new number is the culprit, i created new business portfolio account and added that number and it worked for a day and from next day onwards it started throwing same Error #135000: Generic user error.

My observation is it works out of blue and after 1-2 days successful api calls again it starts throwing same error for 1-2 days and its constantly happening since 15 days.

Then purchased new number and added in new business portfolio, done verification successfully and it worked for couple of days but again same error is coming for that 2nd new number too.

Raised like 3-4 direct support tickets to meta team and they are really really really lazy people. firstly they responds once in 2-3 days first most probably they either closes the ticker with message saying that your api request or endpoint may be invalid or will ask for additional info then would take day or two meantime as this issue is inconsistent shared api explorer with support sometime works and they comes up with solution saying there is no error.

August 3 at 6:47 AM
Santosh