HuskyVoice API, Webhooks, and Workflow Automation

Base URL

Authentication

Authenticate every request using your API key in the Authorization header:

Keep your API key secure and never expose it in client-side code.

Rate limiting

API requests are rate limited per workspace and API key to ensure platform stability. If you exceed the limit, you will receive a 429 Too Many Requests response.

If you need higher throughput for production workflows, please contact support.

Best practices

• Always store and reuse the returned call_id for subsequent operations
• Use Idempotency-Key header when creating calls to handle retries safely
• Validate phone numbers before sending API requests
• Handle terminal and non-terminal call states correctly in your logic
• Never expose API keys in browser-based or mobile client code
• Use the additional_info field to attach CRM or business context

Typical integration flow

1. 1Generate an API key from the Integrations section
2. 2Create a call using POST /calls
3. 3Save the returned call_id for tracking
4. 4Fetch the latest call state using GET /calls/{call_id}
5. 5If needed, cancel the call using POST /calls/{call_id}/cancel while it is still cancellable

Support

Need help with your integration? We're here to assist.

How it works

Each inbound webhook has a unique URL generated inside the HuskyVoice application. Your system can send a JSON payload containing an action and a data object.

Supported actions

Example request — call.create

{
  "action": "call.create",
  "data": {
    "agent_id": "your_agent_id",
    "contact_number": "+919876543210",
    "contact_name": "John Doe",
    "contact_email": "john@example.com",
    "additional_info": {
      "deal_id": "D-100"
    }
  }
}

Example request — call.cancel

{
  "action": "call.cancel",
  "data": {
    "call_id": "the-call-id-to-cancel"
  }
}

cURL example

curl -X POST https://api.huskyvoice.ai/v1/hooks/tok_xxxxxxxxxxxxxxxxx \
  -H "Content-Type: application/json" \
  -d '{
    "action": "call.create",
    "data": {
      "agent_id": "your_agent_id",
      "contact_number": "+919876543210",
      "contact_name": "John Doe"
    }
  }'

Authentication

Requests are authenticated using the secret token embedded in the inbound webhook URL. Treat this URL as a secret. Anyone with access to it may be able to trigger HuskyVoice actions on your behalf.

Security best practices

• Store the inbound webhook URL securely.
• Do not expose it in browser-based or mobile client code.
• Rotate the webhook URL immediately if it is shared or exposed.
• Use optional signature verification for additional protection where supported.

Token rotation

You can rotate the inbound webhook URL from the HuskyVoice application if needed.