Keap HTTP POST SMS Limits

When using Keap (formerly Infusionsoft) to trigger SMS campaigns via HTTP POST to JustCall, be aware of these limits.

Limits

• Keap HTTP POST frequency: Keap sends HTTP POST requests sequentially, not in parallel. Large contact lists may take longer to process.
• JustCall throughput: Messages are subject to your JustCall number's throughput limits (based on 10DLC trust score or toll-free verification status).
• Rate limiting: If Keap sends requests faster than JustCall can process, messages are queued and sent in order.

Best Practices

• Test with small lists first. Send to 10–20 contacts before scaling up.
• Monitor delivery. Check campaign analytics in JustCall after each Keap-triggered campaign.
• Use registered numbers. 10DLC-registered numbers have higher throughput than unregistered numbers.
• Avoid duplicate sends. Ensure your Keap automation doesn't trigger the same campaign multiple times for the same contact.

Related Articles

• HTTP POST SMS Campaign Builder
• Bulk SMS Campaigns and Bulk Texting
• SMS Sending Limits