How It Works

After Authenticx finishes processing a conversation, it evaluates the conversation against the delivery rules configured for your organization. When a conversation qualifies, Authenticx builds a JSON message from your agreed-upon template, authenticates with your system, and sends one POST request per conversation to your endpoint.
Each message includes a matching key, typically the Client Call ID, so your system can tie the data back to the original source record. Every delivery attempt is logged, and failed attempts are retried automatically.

Prerequisites

Before your Authenticx implementation team can activate this integration, the following must be in place:

Step 1: Choose an Authorization Method

Authenticx supports three ways to authenticate with your endpoint. OAuth 2.0 client credentials is recommended.

Token response requirements

For both token-based methods, your token endpoint must:

• Return JSON containing access_token and token_type. Responses missing either field fail.
• Issue access_token as a JWT. Authenticx reads its expiry to decide when to request a new token.

Warning: The header-based token request supports GET only. Credentials can be sent in headers only, not in the query string or request body, and values are sent exactly as stored. Authenticx cannot hash, sign, or base64-encode them (for example, an HMAC signature). If your token endpoint requires POST with custom headers or a JSON body, use OAuth 2.0 client credentials instead.
Tip: If your endpoint needs additional fixed headers (for example, a tenant or tracking header), Authenticx can include them on every request. Header values can include the Authenticx Conversation ID.

Step 2: Choose a Matching Key

Each message must include a matching key so your system can tie the Authenticx data back to its source record. Commonly used keys include:

Recommendation: Include the Authenticx Conversation ID alongside your matching key. It gives both teams a shared reference for support and troubleshooting.

Step 3: Choose the Data to Receive

You choose the field names and structure of the JSON message. Authenticx populates each field from one of the sources below.

Example Message Body

{
  "conversationId": "8f1c2e7a-5b3d-4c9e-a1f0-2d6b7e9c4a11",
  "clientCallId": "CALL-20261027-0042",
  "metadata" : {
    "ANI": "1235554569",
    "DNIS": "0985557654",
    "callDirection": "Inbound"
  },
 "agent" : {
    "Name": "Jane Doe",
    "ManagerId" : "f17da206-3044-483c-9dcc-a56ccbad738f"
  },
 "modelResults" : {
    "summary": "The caller contacted the agent to request an update on a patient's enrollment form and clarify missing information. The agent identified that the initial form was incomplete, lacking essential details such as prescriber information, insurance information, and lab results. The agent offered to resend the form and provided detailed instructions on how to complete it, including specific sections requiring attention and submission methods.",
    "eddy": "true",
    "callResolution": "Next Steps Needed for Customer"
  },
  "QualityScorecard" : {
    "activeListeningScore": "Meets",
    "offerAssistanceScore": "Meets"
  },
  "Transcription" : [
    {
       "Text": "This call may be monitored or recorded for quality and training purposes. Hello, thank you for calling Company Name. This is Jane Doe speaking. How can I help you today?",
	"From": "agent",
	"Timestamp": "2026-07-22T17:33:33.236+00:00"
    },
    {
	"Text": "Hello, this is a representative from a Provider. I wanted to check on a mutual patient's enrollment in your patient support program.",
	"From": "customer",
	"Timestamp": "2026-07-22T17:34:05.045+00:00"
    }
  ],
  "sentAt": "2026-01-01T12:34:56Z"
}

Step 4: Your Endpoint

Your endpoint must meet the following requirements:

Step 5: Provide Details to Authenticx

Collect the following and share them securely with your Authenticx implementation team:

What Authenticx Configures

Your Authenticx implementation team handles the following configuration on your behalf:

Testing & Validation