Application Routing

Assign DIDs to an application to route inbound calls to that application's answer_url and webhook_url. Use one application per environment or workflow when you need separate credentials, webhook destinations, or answer logic.

Integration checklist

An application connects your API key, answer_url, webhook_url, and routing choices. Start with one test application and one simple answer_url that returns a single action. After that works, add gather, transfer, recording, or AI processing in small steps.

Before using the application for real traffic, confirm that the answer_url returns valid JSON quickly, the webhook_url accepts signed events, and the DID or trunk route points to the correct application. Keep separate applications for testing and production so experiments do not affect live callers.

Copy/Paste Examples

Real Request

curl -sS https://api.minivoice.eu/v1/applications \
  -H 'Authorization: Bearer $MINIVOICE_API_KEY'

Real Response

{
  "data": [
    {
      "id": "app_123",
      "name": "Support IVR",
      "customer_id": "cust_123",
      "answer_url": "https://example.com/answer",
      "webhook_url": "https://example.com/webhooks",
      "created_at": "2026-05-29T12:00:00Z"
    }
  ],
  "count": 1
}

Real Webhook Example

{
  "event": "call.completed",
  "created_at": "2026-05-29T12:10:00Z",
  "call": {
    "id": "call_123",
    "customer_id": "cust_123",
    "application_id": "app_123",
    "status": "completed",
    "direction": "inbound",
    "from": "+15551230001",
    "to": "+15551230002"
  },
  "variables": {},
  "data": {}
}

Common Use Case

Configure the application that powers a receptionist IVR, sales routing menu, or appointment reminder line.

Common Failure Case

{
  "error": {
    "code": "invalid_request",
    "message": "answer_url must be a valid URL"
  }
}

Use the error code for branching and log the full response body while testing.