Integration of the Virtual PBX with your own server: when somebody calls one of your voice numbers, we send a POST request (signed JSON) to the URL you configure and we run on the call whatever action your server replies with: talk to the AI assistant, read out a text, transfer to a phone/extension/ring group, offer an options menu, voicemail or hang up.

This way your own business logic decides, in real time and call by call, what to do with each caller: route VIP customers, apply your own opening hours, branch on the status of an order, identify the caller against your CRM, and so on.

In your panel: Voice → Incoming calls, pick the number and choose «Ask my server (interactive actions)». Then configure:
- Your server URL: must be https and a public host (private IPs and redirects are not accepted).
- Maximum wait time: 2 to 8 seconds. The caller is on the line while your server answers, so reply as fast as you can.
- Default action: what we do if your server does not answer in time, returns an error or sends invalid JSON (AI assistant, menu, transfer, voicemail or hang up).
- Verification key: generated when you save; we sign every request with it so you can check the request really comes from us.

The Test button in the panel sends a real test request to your URL and shows you the diagnosis (HTTP status, JSON received and the action that would be executed).

Every request carries the X-Mensatek-Signature header with the HMAC-SHA256 (hexadecimal) of the raw body of the request, computed with your verification key:

X-Mensatek-Signature: sha256=HMAC_SHA256(body, key)

Verification example in PHP:

      $key  = 'YOUR_VERIFICATION_KEY';
      $body = file_get_contents('php://input');
      $sign = $_SERVER['HTTP_X_MENSATEK_SIGNATURE'] ?? '';
      if (!hash_equals('sha256='.hash_hmac('sha256', $body, $key), $sign)) {
        http_response_code(401); exit;
      }
      $data = json_decode($body, true);

We recommend rejecting (401) any request whose signature does not verify.

If your server does not answer within the configured time, replies with a status other than 2xx, or the body is not valid JSON, the call is not lost: the default action configured in your panel runs automatically. Your server must reply 2xx with Content-Type: application/json.

Reply with a JSON object containing the accion field plus the extra fields that apply to that action (any others are ignored):

Optional common fields, valid with any action:
- idioma: TTS voice and language in the form xx-XX:n (n: 1 female, 2 male). E.g. es-ES:1, pt-PT:1, en-US:1.
- grabar: true/false, turns recording of this call on or off.

Response examples:

      // Send a VIP customer straight to their account manager
      { "accion": "desviar", "destino": "+34600000001" }

      // Send the call to ring group 2 (rings on several extensions)
      { "accion": "desviar", "destino": "grupo:2" }

      // Custom greeting and AI assistant
      { "accion": "ia", "texto": "Hello Mr Garcia, you are through to the MyCompany assistant." }

      // A menu saved in the panel
      { "accion": "ivr", "plantilla": "Main menu" }

      // Read out a notice and hang up
      { "accion": "reproducir", "texto": "Your order 1234 ships today. Thank you for calling." }

      // Voicemail with your own announcement and recording enabled
      { "accion": "buzon", "texto": "We cannot take your call right now, please leave a message.", "grabar": true }

Inline menu format (menu): the very same object produced by the visual editor in the panel. Keys: locucion (the text read out offering the options; it accepts the (MP3:file) and (PAUSA:seconds) markers), esMenuDTMF = 1, and one key per keypad digit holding the option: Accion (1 repeat · 2 notify a URL · 3 notify by email · 4 transfer to a phone · 6 hang up · 7 AI assistant · 8 transfer to an extension · 9 transfer to a ring group), Valor (the target of the action), Palabra (optional: the caller may SAY it instead of pressing the key), LocucionPrevia and LocucionFinal (optional, played before and after the action).

      {
        "accion": "ivr",
        "menu": {
          "locucion": "For sales, say sales or press 1. For support, press 2.",
          "esMenuDTMF": 1,
          "1": { "Accion": "9", "Valor": "grupo:1", "Palabra": "sales", "LocucionPrevia": "Putting you through to sales." },
          "2": { "Accion": "8", "Valor": "ext:102" }
        }
      }

The evento field of the request tells you at which point of the call we are asking (ignore any event you do not recognise by replying with your default action):

New events will be added to this specification keeping the same format and signature.

Any response may include the contacto object with the caller's details according to your CRM:

      { "accion": "desviar", "destino": "grupo:2",
        "contacto": { "nombre": "Jose Munoz (VIP)", "email": "jmunoz@customer.com", "variable_1": "Order 8812" } }

The nombre field is shown on the agent's softphone when the call is transferred (taking priority over the contacts saved in the panel). The remaining fields are used by the smart voicemail and by upcoming features.