dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

storkit: create 382_story_whatsapp_transport_supports_twilio_api_as_alternative_to_meta_cloud_api

Browse Source
This commit is contained in:
dave
2026-03-24 16:41:13 +00:00
parent 88b02cf746
commit aad583defd
1 changed files with 22 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
.storkit/work/1_backlog/382_story_whatsapp_transport_supports_twilio_api_as_alternative_to_meta_cloud_api.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: "WhatsApp transport supports Twilio API as alternative to Meta Cloud API"
---
# Story 382: WhatsApp transport supports Twilio API as alternative to Meta Cloud API
## User Story
As a user, I want to use Twilio's WhatsApp API instead of Meta's Cloud API directly, so that I can avoid Meta's painful developer onboarding and use Twilio's simpler signup process.
## Acceptance Criteria
- [ ] bot.toml supports a `whatsapp_provider` field with values `meta` (default, current behavior) or `twilio`
- [ ] When provider is `twilio`, messages are sent via Twilio's REST API (`api.twilio.com`) using Account SID + Auth Token
- [ ] When provider is `twilio`, inbound webhooks parse Twilio's form-encoded format instead of Meta's JSON
- [ ] Twilio config requires `twilio_account_sid`, `twilio_auth_token`, and `twilio_whatsapp_number` in bot.toml
- [ ] All existing bot commands and LLM passthrough work identically regardless of provider
- [ ] 24-hour messaging window logic still applies (Twilio enforces this server-side too)
## Out of Scope
- TBD