API TCPA Enforcement 

Update Summary:

• If an API request is made to /call outside of legally allowed calling hours per TCPA (Telephone Consumer Protection Act), the system rejects the request with a 406 Not Acceptable response.
• If a campaign ID is provided in the request, the contact is automatically added to the campaign and will be called at a permissible time.  
• When successfully queued, the API returns a 200 response to confirm the contact is scheduled for a future call.
• For more details, please reference to https://lets.taalk.ai/doc/swagger

What You Need to Do:

1. Handle the 406 Error Gracefully

• If your system receives a 406 Not Acceptable response, ensure that your application logic does not retry the call immediately.
• Instead, confirm whether a campaign ID was included in the request. If so, the contact will be auto-queued. 
• If no campaign ID was included, you may need to manually reschedule the call within permissible hours.

2. Ensure Campaign-Based Calls

• If you anticipate making calls that may fall outside TCPA-compliant hours, ensure your API request includes a campaign ID so that calls can be automatically queued for later.

3. Monitor API Responses

• If you see 406 errors frequently, it may indicate that calls are being attempted during restricted times.
• You can adjust your system to check TCPA-compliant calling hours before making the API request.

Why This Matters:

• Ensures TCPA Compliance: Helps prevent potential fines or violations by blocking calls during restricted hours.
• Automatic Call Scheduling: If a campaign ID is provided, the system ensures the call happens later, reducing the risk of missed connections.
• Better Call Management: Encourages scheduling practices that respect compliance rules without disrupting campaign operations.

https://knowledge.taalk.ai/compliance-/call-api-tcpa-update