Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(sdk): mark only the media convert methods as OPERATOR in §18.1
Yudhi Armyndharis9b27bbb90dcc
diff --git a/docs/18-sdk-design.md b/docs/18-sdk-design.mdindex b7aba8869..e16b9bf42 100644--- a/docs/18-sdk-design.md+++ b/docs/18-sdk-design.md@@ -42,7 +42,7 @@ All five SDKs expose the same fluent surface:| `templates` | list, get, create, update, delete || `profile` | setProfileName, setProfileStatus, setProfilePicture, deleteProfilePicture || `calls` | rejectCall, createLink |-| `media` | conversionStatus, convertVoice, convertVideo _(OPERATOR)_ |+| `media` | conversionStatus, convertVoice _(OPERATOR)_, convertVideo _(OPERATOR)_ || `health` | check, live, ready |The tables describe `main`. The 0.5.0 registry builds do not include `sessions.getProxy`, `sessions.updateProxy` or `messages.clickButton` (`get_proxy`, `update_proxy` and `click_button` in Python; `GetProxy`, `UpdateProxy` and `ClickButton` in Go); they ship with the next SDK release. The webhook signature helpers (`verifyWebhookSignature`, `verify_webhook_signature`, `VerifyWebhookSignature`, `WebhookSignature.verify`, `WebhookSignature::verify`), the `WebhookDelivery` types and the API error code, retry-delay and headers accessors are not in 0.5.0 either; they also ship with the next SDK release. Nor is the Java fallback to `UNKNOWN`: 0.5.0 decodes a response enum value it does not recognise to `null` (`MessageType` and `ChatKind` included), and `SessionStatus`, `DeliveryStatus` and the other response enums that lack an `unknown` wire value have no `UNKNOWN` constant there.