wdevs/whatshooked
5
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add Meta API version setting for a Meta account #2

New Issue
Open
opened 2026-04-09 20:48:32 +00:00 by sgcommand · 0 comments
sgcommand commented 2026-04-09 20:48:32 +00:00
Member
Copy Link

Add a configurable Meta Graph API version setting per Meta/WhatsApp Business account.

Why

  • Meta versions change over time and may differ between deployments
  • Hardcoding the API version makes upgrades and compatibility testing harder
  • Per-account configuration gives better flexibility during rollouts/migrations

Suggested scope

  • Add api_version (or similar) to Meta account configuration
  • Use that version when building Graph API requests
  • Provide a sensible default if not set
  • Validate/normalize the configured value where appropriate

Acceptance criteria

  • Meta account config supports an API version field
  • Outbound Meta API requests use the configured version
  • Existing configs continue working via default behavior
  • Documentation includes the new setting and an example
Add a configurable Meta Graph API version setting per Meta/WhatsApp Business account. ## Why - Meta versions change over time and may differ between deployments - Hardcoding the API version makes upgrades and compatibility testing harder - Per-account configuration gives better flexibility during rollouts/migrations ## Suggested scope - Add `api_version` (or similar) to Meta account configuration - Use that version when building Graph API requests - Provide a sensible default if not set - Validate/normalize the configured value where appropriate ## Acceptance criteria - Meta account config supports an API version field - Outbound Meta API requests use the configured version - Existing configs continue working via default behavior - Documentation includes the new setting and an example
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/whatshooked#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?