when iam trying to send whatsapp message with test number .. it showing error message like whatsapp test numbers are currently unavailable ..it is asking me to add phone number why

I'm trying to create a simple ChatBot for WhatsApp and have hit a brick wall adding a phone number to the account. I've been Googling and trying various things for the last week and have gotten no further.

I have set up an App in my Facebook Developer account with WhatsApp; In API Setup I've added a new number (paid number that's guaranteed to work with WhatsApp, not one of the freebie ones), verified it by SMS and got an phone ID for that new number. However, when I try and 'generate access token', I get the following error:

If I try to register or verify the number via API, using either the /PHONE_ID/register or /PHONE_ID/request_code endpoints, I get the same error message in the terminal saying the PHONE_ID does not exist, yet if do a check of /BUSINESS_ID/phone_numbers it returns a response with that very same PHONE_ID, eg:

{    "data": [       {          "verified_name": "Business Name",          "code_verification_status": "VERIFIED",          "display_phone_number": "+44 XXXX XXXXX",          "quality_rating": "UNKNOWN",          "platform_type": "NOT_APPLICABLE",          "throughput": {             "level": "NOT_APPLICABLE"          },          "webhook_configuration": {             "application": "https://foo.bar/mywebhook.php"          },          "id": "PHONE_ID"       }    ],    "paging": {       "cursors": {          "before": "XXXXXX",          "after": "XXXXX"       }    } } 

I have made sure the business itself is verified and has a payment source. The phone number name has been approved. I cannot find any unmissed alerts in WhatsApp manager, and yet the number remains 'pending'. In the API config, the drop-down shows the number, but is unselectable as it's saying it's not registered. Oh my days...

Any help would be much appreciated. I'm tearing my hair out over this one.

Error WhatsApp test numbers are currently unavailable. Contact support.

I'm trying to create a message template for whatsapp business and i keep getting an error. Following the docs, I think my implementation is correct. If buttons are not included(with dynamic content its pretty much easy on the meta dashboard, but here I'm try to use button with dynamic content which is not possible on the dashboard so I have to go the curl way but it's not working. below is my implementation(had to switch to python thinking i might get on to something)

import requests from requests.structures import CaseInsensitiveDict url = "https://graph.facebook.com/v20.0/whatsapp_busines_id/message_templates" headers = CaseInsensitiveDict() headers["Authorization"] = "Bearer YOUR_ACCESS_TOKEN" headers["Content-Type"] = "application/json" data = """ {         "name": "payment_success_property_contact",         "language": "en",         "category": "UTILITY",         "components": [           {             "type": "HEADER",             "format": "TEXT",             "text": "Payment Successful"           },           {             "type": "BODY",             "text": "Hi there! Great news! Your payment for \"{{1}}\" is successful. Please contact the owner via WhatsApp or normal call to visit and check the property. After your visit, you can confirm or cancel the payment.\n\nEnjoy your visit!",             "example": {               "body_text": [                 "Seaside Villa"               ]             }           },           {             "type": "FOOTER",             "text": "Nanohunt Software"           },           {             "type": "BUTTONS",             "buttons": [               {                 "type": "URL",                 "text": "Contact via WhatsApp",                 "url": "https://wa.me/{{2}}",                 "example": {                   "parameters": [                     {                       "type": "text",                       "text": "YOUR_PHONE_NUMBER"                     }                   ]                 }               },               {                 "type": "PHONE_NUMBER",                 "text": "Call Owner",                 "phone_number": "{{2}}",                 "example": {                   "parameters": [                     {                       "type": "text",                       "text": "YOUR_PHONE_NUMBER"                     }                   ]                 }               },               {                 "type": "URL",                 "text": "Confirm or Cancel Payment",                 "url": "{{3}}",                 "example": {                   "parameters": [                     {                       "type": "text",                       "text": "https://yourwebsite.com/transaction/TRANSACTION_ID"                     }                   ]                 }               }             ]           }         ]       } """ resp = requests.post(url, headers=headers, json=data) print(resp.json()) 

So after running it i get

mbishu@fedora:~/Desktop/nanohuntapi$ python template.py {'error': {'message': '(#100) The parameter name is required.', 'type': 'OAuthException', 'code': 100, 'fbtrace_id': 'AywCoC2brI1L5kRVmtbHD-c'}} 

I search the internet so far but no viable solution

We are integrating WhatsApp Cloud API for our app through the Business API Gateway. Here's what we have done so far:

Successfully generated a short-lived access token via the Graph API. Used the token, version, and ID for API calls, which worked fine. Meta approved our app review request. However, the issue arises when we attempt to generate a long-lived (or permanent) access token. After making the request, our account gets temporarily blocked or restricted.

Does anyone know why this might be happening or what steps we need to take to avoid the restriction when generating a long-lived access token?

We're following Meta's guidelines for generating access tokens. Short-lived tokens work fine, but the issue is specific to the long-lived token generation. We've made sure all API calls adhere to the required permissions and scopes. Any guidance or insights would be appreciated.