Sending whatsapp throug cloud api
Cloud api is giving success on sending whatsapp mesage but message is not received on respective number. I am using a template created by me
Tony-Marketing-API.cn is a vibrant community dedicated to Facebook, Meta,Google Ads api, app development, Instagram, and related technologies. It offers valuable bug solutions, troubleshooting cases, and problem-solving strategies shared by users. Stay updated with real-world solutions, development tips, and the latest trends in digital marketing and app development.
Cloud api is giving success on sending whatsapp mesage but message is not received on respective number. I am using a template created by me
Hi,
We'd like to increase the messaging limit for our WhatsApp account and we have started 11k+ conversations with unique customers in the last 7 days. We have waited for a 24 hour window too. However, we still didn't observe an increase in the limit.
Can someone please help us out with that as we have to go live soon?
Thanks, Thiagarajan
While doing setup for WhatsApp Business Platform API, the business profile is selected but when clicked on Continue for further setup below error is received 'Onboarding Failure You have been temporarily blocked from performing this action.'
And before this error earlier received below error 'Onboarding Failure Please Reply in some time or contact support to get issue fixed'
I'm working on an ASP.NET MVC app using SignalR that implements a WhatsApp Chat, where the user can send a message from the app to a WhatsApp number, and from there it can be answered, thus showing the response on the page. So far, I've got to separate the messages sent from the WhatsApp account to each tab on different browsers, as I'm using the SignalR connectionID
, given that each time a page is loaded, a new connection is established.
From the client, I send the messages as follows
connection.invoke("SendMessage", user, message).catch(function (err) { return console.error(err.toString()); });
and from the server, I send the message to all clients as follows
public async Task SendMessage(string user, string message) { await Clients.All.SendAsync("ReceiveMessage", user, message); }
To a particular client, I send a message with the connectionID
await _hubContext.Clients.Client(idConexion).SendAsync("ReceiveMessage", "Message:", textMessage[0].Text.Body);
What I'd like is that the same browser is considered as only one connection, no matter how many tabs are opened. I know from the documentation and other StackOverflow questions that each tab opened is a different connection, but I just need to broadcast the same message to all active tabs of a browser. My current logic is that messages are sent to a particular connection, using the unique WAMID from each message from the WhatsApp Business API.
In the page setup on Meta For Developers it says that the account (test number) does not exist in the Cloud API. I was previously able to run tests normally with the provided test number (receiving messages on my personal phone), but since yesterday afternoon, I've been getting some message like:
"Failed to send message. The account does not exist in the Cloud API. Use the /register API to create an account first."
Making the request in Postman, I have the following response:
"error": { "message": "The account is not registered", "type": "OAuthException", "code": 133010, "error_subcode": 2593006, "is_transient": false, "error_user_title": "The account does not exist", "error_user_msg": "The account does not exist in the Cloud API. Use /register API to create an account first.", "fbtrace_id": "A6fN7xoCSrj2t1dW_Qvv5d0" }
In my Flutter project (VSCode), the Debug Console also shows:
"flutter: {error: {message: The account is not registered, type: OAuthException, code: 133010, error_subcode: 2593006, is_transient: false,..."
Despite my best efforts, I've reached a dead end... help me please.
I've tried everything I can think of: checking all the API settings, sending messages to different numbers, reviewing the documentation, and searching the internet for similar issues. But nothing seems to work. I just need to get the tests running again.