Interrupción parcialshare-external
Added number and verified it by SMS, but when creating access token I get an error and number is forever pending
1

I've added a real number to my WhatsApp App, but as per the question title, I'm getting an error saying the object id (the PHONE_ID) "does not exist, cannot be loaded due to missing permissions, or does not support this operation".

I've gone through every screen I can find in WhatsApp Manager and Meta Developers, and can't find anything obvious that I'm missing. I did a call to /BUSINESS_ID/phone_numbers and it confirmed that the new number is connected to my account and the phone ID is valid, 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"
      }
   }
}

However, any calls I make to the API such as /PHONE_ID/register or /PHONE_ID/request_code all come back with object does not exist, cannot be loaded due to missing permissions, or does not support this operation. What on earth am I missing here.

The business account is verified and has a payment source.

Pete
Enviada hace 2 meses aproximadamente
Pete

Still working on this and trying to pick apart the error message to rule out what might be causing it. The first one, 'object does not exist' clearly can't be true. The last one, 'does not support this operation' doesn't seem plausible as it's an action the management page itself is trying to perform. The second one though, might be it. So I created a new system user access token with EVERY available permission. Still no joy. Must be some other config checkbox that I'm missing.

2 de octubre a las 9:04
Respuesta seleccionada
1

Ok, so I have managed to get a little further, but with WhatsApp API it always feels like one step forward and two steps back.

To resolve this particular problem (your mileage may vary), I regenerated a temporary access code but made sure I edited the connection and then gave my user account access to all WhatsApp projects current and future. The error message went away and I could send a test to my business number and also get webhooks sending replies to my server. However, still getting permissions error when trying to send a message via the API in reply and when I tried to generate a new access code for an Admin system user I get an error saying the query failed. But I'll save that for a separate post.

3 de octubre a las 5:16
Pete