POST | /topics/{BotId}/subscriptions | ||
---|---|---|---|
POST | /topics/{BotId}/subscriptions/{MSISDN} |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
BotId | path | string | No | |
MSISDN | path | string | No | |
Message | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | string | No | |
ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /topics/{BotId}/subscriptions HTTP/1.1
Host: telegram-notifications.dev.k8s.sandboxaddis.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"botId":"String","msisdn":"String","message":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"id":"String","responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}