You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks progress against things that will be included in an upcoming v9 release of this SDK. Any features that constitute breaking changes will also be noted here whilst progress continues towards the milestone.
Update type names to prefix with Whatsapp as relevant. This should make types more clear when operating with WhatsApp Business Accounts and Meta Business Accounts in tandem. This may be included in a minor update with some exported aliases.
Use positional parameters for required IDs: sdk.etc({ someID, etc }) -> sdk.etc(someID, { etc }). Especially when the ID is the only required parameter and no other parameters are used, it can be cumbersome to create an entire options object - even more so when the ID's variable doesn't exactly match the expected option field name. sdk.etc(someID) is much clearer than sdk.etc({ someOtherID: someID }).
Only use arrays for fields to be included, not Record<string, boolean>.
Fix the mismatch of API method names, e.g. getPhoneNumber() and get(). They should probably all use a short name as the resource context is implied from the SDK call (sdk.someResource.method()).
This discussion was converted from issue #367 on April 17, 2026 15:23.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This issue tracks progress against things that will be included in an upcoming
v9release of this SDK. Any features that constitute breaking changes will also be noted here whilst progress continues towards the milestone.Whatsappas relevant. This should make types more clear when operating with WhatsApp Business Accounts and Meta Business Accounts in tandem. This may be included in a minor update with some exported aliases.sdk.etc({ someID, etc })->sdk.etc(someID, { etc }). Especially when the ID is the only required parameter and no other parameters are used, it can be cumbersome to create an entire options object - even more so when the ID's variable doesn't exactly match the expected option field name.sdk.etc(someID)is much clearer thansdk.etc({ someOtherID: someID }).fieldsto be included, notRecord<string, boolean>.getPhoneNumber()andget(). They should probably all use a short name as the resource context is implied from the SDK call (sdk.someResource.method()).All reactions