Developer FAQ
DeBox Developer FAQ / Troubleshooting
This page covers high-frequency integration issues and practical diagnosis paths.
Primary docs for new integrations:
1. Which document should I start with?
Choose by integration path:
- Field definitions, enums, success/error samples: OpenAPI.
- Go SDK with long polling: GO-SDK.
- Webhook mode: GO-SDK Webhook.
2. Why does getUpdates return no messages?
Most likely webhook is already configured.
In DeBox, webhook and long polling are strictly mutually exclusive:
- With webhook configured, webhook is the effective receive path.
- To use long polling, clear webhook config first.
3. How should I fill chat_id and chat_type?
chat_type=group:chat_idmust be groupgid(e.g.cc0onr82).chat_type=private:chat_idmust be useruser_id(invite code).
These two fields are the primary routing keys for sendMessage / editMessage.
4. For parse_mode=image/video/file, what should content be?
content must be a public URL:
image: image URLvideo: video URLfile: file URL
For text modes (richtext/text/Markdown/MarkdownV2/HTML), max content length is 5000 chars.
5. How to secure webhook callbacks?
Webhook callback includes header X-API-KEY = Webhook Key.
Your backend must validate it before processing payload.
Troubleshooting note:
- Webhook Key rotates when webhook URL changes.
- Sync the new key to your backend validator.