Understanding DoubleTick API Rate Limits
When you send messages or perform actions using DoubleTick, there are limits on how many requests you can make per second or per minute. These limits are called rate limits, and they help keep the system stable and prevent delays for everyone.
If you’re not very technical, don’t worry—this article will explain everything in simple terms and show you the key numbers you need to know.
What Are Rate Limits?
Think of DoubleTick as a busy post office. You can send letters (messages, media, or updates), but if you try to send too many at once, the system slows down to handle the load.
A rate limit tells you:
How many requests you can send
How fast you can send them
If you exceed the limit, the system will temporarily block your extra requests until it’s safe to continue. This keeps your messages reliable and prevents errors.
Common Actions and Their Rate Limits
Here’s a simple table showing the most common things you can do in DoubleTick and how often you can do them.
Send Template Message
600 requests per second
Templates are WhatsApp-approved messages. These can be sent at high scale but should still be spaced in bulk campaigns.
Send Text Message
150 requests per second
Text messages are lightweight and can be delivered quickly.
Send Video Message
15 requests per second
Videos require heavy processing, so fewer can be sent at once.
Send Audio Message
15 requests per second
Audio files are similar in size to video, so limits are lower.
Send Image Message
100 requests per second
Images are faster than video but slower than plain text.
Send Document Message
25 requests per second
Documents like PDFs or Excel files take longer to upload and deliver.
Send Location Message
5 requests per second
Location requests require additional validation, so the limit is low.
Send Interactive Message (Buttons)
100 requests per second
Interactive messages such as reply buttons can be sent quickly.
Send Interactive List Message
100 requests per second
List-type menus follow the same rate limit as interactive buttons.
Broadcast Messages
5 requests per second
Broadcasts send to many users at once, so limits are strict to avoid overload.
Export Chats
1 request per second
Chat exports take time to generate, so only one can run at a time.
Fetch Chat Messages
25 requests per second
Message history can be pulled frequently but within limits.
Check Wallet Balance
100 requests per second
Balance checks are lightweight and allowed often.
Customer Details Lookup
25 requests per second
Customer info fetch requests are moderate in frequency.
Assign Tags / Custom Fields
300 requests per second
Bulk tagging is supported at scale for automation use cases.
Remove Tags / Fields
5 requests per second
Removal actions are more controlled and slower.
Block / Unblock Customer
5 requests per second
Customer safety actions have strict limits to prevent misuse.
Assign Customer to Agent
25 requests per second
Agent assignment is allowed frequently in support workflows.
Team Member Assign / Unassign
25 requests per second
Used in team routing workflows, allowed moderately.
Team Member Logout
5 requests per second
Logout actions are limited for security reasons.
Manage Teams & Roles
1–10 requests per second
Team setup actions are occasional, not high-frequency.
Upload Media
100 requests per second
Media uploads are supported at a good scale.
Register Webhook
1 request per second
Webhook setup is rare, so limits are strict.
View Webhooks
1 request per second
Webhook listing is limited to avoid repeated polling.
Deregister Webhook
1 request per second
Webhook removal is controlled for system safety.
⚠️ Tip: If you’re sending multiple messages at once, try to space them out instead of sending all at once. This prevents hitting the rate limit and ensures your messages go through smoothly.
Why This Matters for You
Reliable Messaging: Following rate limits ensures all your messages are delivered.
Avoid Errors: Sending too many requests at once can cause errors or failed messages.
Better Planning: Knowing these limits helps you schedule campaigns and automations without interruptions.
Quick Tips for Non-Tech Users
Use Automated Campaigns Carefully – When sending broadcasts or campaigns, don’t exceed the recommended limits.
Media Messages Take More Time – Videos, audio, and documents need extra processing. Send in smaller batches.
Check Before Sending Templates – Since templates have very strict limits, plan their use wisely.
Ask for Help – If you’re unsure about limits or face errors, reach out to DoubleTick Support before sending a large batch.
By keeping these limits in mind, you can make the most out of DoubleTick while keeping your messages reliable, fast, and safe.
Last updated