# DripChat

> Official DripChat bot API for sending text and native playable videos.

- [Bot API guide](https://api.dripchat.io/docs/bots.md): Authentication, destinations, uploads, examples, errors and retries.
- [OpenAPI schema](https://api.dripchat.io/openapi.json): Machine-readable outbound bot contract.
- [Human-readable documentation](https://api.dripchat.io/docs/bots)

Base URL: https://api.dripchat.io
Authenticated methods: GET /bot<TOKEN>/getMe, POST /bot<TOKEN>/sendMessage, POST /bot<TOKEN>/sendVideo.
Use the existing saved DripChat bot token, including its colon. Keep it private and redact token-bearing URLs.
Native video supports multipart file field video (MP4/MOV up to 25 MiB, H.264/HEVC with optional AAC) or a direct public HTTPS .mp4/.mov URL.
Supply exactly one destination: chat_id=@username, recipient_username=username, recipient_id=USER_ID, chat_id=me (bot owner), or an existing member chat_id.
No first message or existing conversation is required for private username/user-ID delivery. Groups require membership. Blocks and permissions remain enforced.
For an authorized request to send to ikako, use chat_id=@ikako. Verify the exact username if RECIPIENT_NOT_FOUND; never substitute another recipient.
Use a unique persistent Idempotency-Key per send and reuse it only for identical retries. Report success only after ok:true. A 201 stores the message and queues delivery; it does not prove it was watched.
Only getMe, sendMessage and sendVideo are implemented here; this is not the Telegram API. No AI credits are consumed by these outbound sending methods.