Nest phone numbers inside their parent WhatsApp Business Accounts in MetaOptions#387
Merged
Nest phone numbers inside their parent WhatsApp Business Accounts in MetaOptions#387
Conversation
…MetaOptions
This provides a more intuitive configuration and more easily allows multi-tenancy. VerifyToken also moved down to the specific Account.
New config shape:
Meta:Accounts:{accountId}:Token = <bearer-token>
Meta:Accounts:{accountId}:PrivateKey = <PEM key> # optional, for Flows
Meta:Accounts:{accountId}:Numbers:0 = <numberId>
Removes the flat Meta:Numbers and root Meta:PrivateKey; the token
for a given phone number ID is found by iterating account entries.
Flow data decryption strategy:
- If the webhook URL includes /{accountId}, use that account's key
- Otherwise, try all configured account keys until one decrypts
Azure Functions: two [Function] methods per route (optional params unsupported)
ASP.NET Core: single handler with optional accountId parameter on both routes
Member
Author
|
🧪 Details on Ubuntu 24.04.4 LTSfrom retest v1.1.0 on .NET 10.0.5 with 💜 by @devlooped |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This provides a more intuitive configuration and more easily allows multi-tenancy. VerifyToken also moved down to the specific Account.
New config shape:
Meta:Accounts:{accountId}:Token =
Meta:Accounts:{accountId}:PrivateKey = # optional, for Flows
Meta:Accounts:{accountId}:Numbers:0 =
Removes the flat Meta:Numbers and root Meta:PrivateKey; the token for a given phone number ID is found by iterating account entries.
Flow data decryption strategy:
Azure Functions: two [Function] methods per route (optional params unsupported)
ASP.NET Core: single handler with optional accountId parameter on both routes