Commit activity
Last 12 weeks · 16 commits
Community health
5 of 6 standards met
75
✓README✓License✓Contributing✓Code of Conduct✓Issue Template○PR Template
Recent PRs & issues
Active · Last activity 12h ago
See all on GitHub →
Error Creating AdSet Redirecting to WhatsApp: "WhatsApp phone number is not linked to your account"OpenIssue
Description When attempting to create an AdSet that redirects to WhatsApp using the Marketing API, I encounter the following error: The same configuration works perfectly fine when created via Meta Ads Manager. However, it fails when trying to create it programmatically through the API. Below are the details of the request being sent and other relevant context. Steps to Reproduce 1. Retrieve WhatsApp numbers using the following endpoint: 2. Use the retrieved and other necessary information to create an AdSet with the following payload: 3. The API responds with the error described above, indicating that the WhatsApp phone number is not linked to the account. Expected Behavior The AdSet should be successfully created using the API with the same configuration that works when created through Meta Ads Manager. Actual Behavior The API returns an error stating: . Additional Context API Scopes Used: The phone number is correctly retrieved using the field of the endpoint and is linked to the same business account used for the ad campaign. When I check the AdSet created through Meta Ads Manager in the Graph API Explorer, the structure matches the payload sent through the API. Steps Tried to Resolve Confirmed that the phone number is linked to the correct business account. Verified that the access token has all necessary permissions. Successfully created an AdSet using the same phone number via Meta Ads Manager. Compared the structure of the AdSet created via Ads Manager and the payload sent via the API. Request Please confirm if there are additional steps required to link the WhatsApp phone number to the ad account when using the API. Verify if this is a known bug or limitation in the API. Provide guidance on resolving this issue programmatically.
Version Tag 24.0.1 latest Version Downloads (Last 7 Days) Tag 24.0.1 115,772 latest
The GitHub release v25.0.1 was published, but the npm package is still at v24.0.1. npm latest: 24.0.1 (https://www.npmjs.com/package/facebook-nodejs-business-sdk) GitHub latest release: 25.0.1 Could you please publish the latest version to npm?
Recent fixes
The previous implementation lacked a robust mechanism for handling potential context overflow errors during the execution of API requests. This PR introduces a standardized detection mechanism for context overflow scenarios, leveraging the provided utility functions to inspect error messages. This improvement ensures that the application can gracefully identify and respond to requests that exceed the model's token limitations, enhancing the overall reliability of the SDK.
Hello I started recently to get these errors when calling various endpoints, for instance getCampains or getInsightsAsync or adreportrun.getInsights first error encountered mar. 4, 2025 and `` Seems like the response body returns an empty value or an error HTML be hard to debug the content on my side If need be for reproduction purposes i can patch the sdk to log the full HTTP response, but I wanted at least to know if it is a known bug that can be ignored/retried, or not I didn't have this error before migrating to release 24.0.1 of the SDK Thank you
Structured data for AI agents
Repository: facebook/facebook-nodejs-business-sdk. Description: Node.js SDK for Meta Marketing APIs Stars: 612, Forks: 251. Primary language: JavaScript. Languages: JavaScript (100%). Homepage: https://developers.facebook.com/docs/business-sdk Latest release: v26.0.0 (2w ago). Open PRs: 15, open issues: 67. Last activity: 12h ago. Community health: 75%. Top contributors: jingping2015, stcheng, satwikareddy3, vicdus, HeyMultiverse, marksliva, zanyaziz, davit-y, donglinw-fb, supasate and others.