AlloMia by MEDFAR
Back to For your IT team

Testing a connection

Before you turn a tool on for an AI agent, send a test request from its Testing tab. You see exactly what AlloMia sent and what your software answered.

Last updated: October 7, 2026

In this article

Before you start

  • On the Connection tab, give each variable a sample Value. The test puts these values in the request. Use test data: during calls, AlloMia also uses Value when the agent leaves an optional variable out.
  • The test uses what’s on screen, even before you save. For OAuth2, save the tool and click Get Token on the Authentication tab first: the test uses the saved OAuth2 settings.
  • The request is real. A test that creates a booking creates one. Use a test environment if you have one, or cancel what the test creates.
  • The request comes from AlloMia’s servers, so your URL must be reachable from the internet.

Run a test

  1. In the menu on the left, click Tools & Actions, then Tools, and click the tool.
  2. Click the Testing tab.
  3. Click Test Tool.
  4. If a Configuration Errors box appears, fix what it lists, then click Test Tool again.

Read the result

  • Response tab: the Status, with the HTTP code (green from 200 to 299), and the body your API returned.
  • Request tab: the URL, method, headers and body AlloMia sent, with your sample values filled in. Compare it with your API documentation. It shows your credentials in clear text, so take care when you share a screenshot.
  • Expand View opens the result in a larger window.

How a test differs from a call

  • GET: the test adds each variable that isn’t in the URL to the query string. Calls don’t. Put every variable in the URL yourself, for example ?date={{date}}.
  • Number and Boolean variables: the test sends every sample value as text, in quotes. In calls, numbers and true or false are sent without quotes.
  • Bearer Token and Basic Auth: the test doesn’t send the Authorization header the way calls do. Securing a connection to your clinic software explains how to test them.
  • Timeout and Retry Count: the test doesn’t use them. It sends the request once and waits.
  • DELETE: the test sends no body. Calls send the Request Body, if there is one.
  • Call ID: {{callId}} is filled in with zeros.
  • Messages: the test doesn’t say the messages from the Messages tab.

Then try it in a call

  1. Turn the tool on for the AI agent. See Turning actions on or off for your AI agent.
  2. On the agent, click Speak with Agent and ask something that needs the tool. See Trying your AI agent yourself.
  3. In Call Logs & Analytics, open the call. In the Conversation Transcript, click the Tool Call line to see the values the agent sent, and the Tool Result line to see your API’s answer.

If something goes wrong

  • No status code: AlloMia couldn’t reach the URL (address, DNS, firewall or certificate), or couldn’t get an OAuth2 token.
  • 400 or 422: the body or the parameters don’t match what your API expects. Compare the Request tab with your documentation. In the body, placeholders must have no quotes.
  • 401 or 403: your API refused the credentials. See Securing a connection to your clinic software.
  • 404: check the URL path, and that each placeholder in it has a sample Value.
  • 405: change the HTTP Method.
  • 500 to 599: an error in your software. Check its logs.
  • The test takes a long time: during calls, a request that takes longer than the Timeout fails. Raise the Timeout or speed up the endpoint.