| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BotId | query | string | No | |
| Token | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | string | No | |
| WebhookUrl | 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 /json/reply/CreateOrUpdateBot HTTP/1.1
Host: telegram-notifications.dev.k8s.sandboxaddis.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"botId":"String","token":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":"String","webhookUrl":"String","responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}