Yaqeen AgentIQ

Compliance & QA Analytics API — Complete Integration Guide This REST API provides intelligent, Bedrock-powered post-call analytics. It allows clients—including Bedrock Agents, OpenAI functions, and traditional applications—to transcribe calls, evaluate compliance, ask follow-up questions, and generate detailed reports. Although REST APIs are stateless by design, this API supports multi-turn context via a persistent SESSION_ID. API Endpoint POST https://8g6kw1zm02.execute-api.us-east-1.amazonaws.com/prod/invoke  Authentication All requests must include a valid API key: x-api-key: YOUR_API_KEY

Request Schema Headers Content-Type: application/json x-api-key: YOUR_API_KEY Body (JSON) { "INPUT_TEXT": "Transcribe the call s3://your-audio-bucket/ReliantFinance-abc123.wav", "SESSION_ID": "Session_123" } Parameters Field Type Required Description INPUT_TEXT string Yes Natural language instruction (e.g., "Transcribe call s3://...") SESSION_ID string Yes Unique identifier to maintain session context (e.g., per call or per user)

Response { "sessionId": "Session_123", "agentResponse": "The transcription for the call with ID 'abc123' has been initiated. You will be notified once it is complete." } Subsequent requests using the same SESSION_ID will preserve conversational memory, enabling multi-turn interaction: Example Follow-Up: { "INPUT_TEXT": "Is the transcription done?", "SESSION_ID": "Session_123" }

{ "sessionId": "Session_123", "agentResponse": "The transcription for call ID 'abc123' is complete." }

Context Management via SESSION_ID Although HTTP is stateless, the Bedrock Agent or OpenAI system maintains state through the SESSION_ID passed in each request. This allows the agent to: • Remember which call was previously transcribed • Respond to follow-up questions intelligently • Generate reports based on prior instructions The SESSION_ID can be a UUID, call ID, or any custom string, and should be reused throughout a single session. Integration with Bedrock Agent / OpenAI Function Calling

1. Define a REST Tool (for Bedrock) If using Bedrock Agent with Action Groups, define this API as a REST tool and allow your agent to invoke it with the contract below.
2. OpenAI Function Calling Integration OpenAI's function calling can be used to invoke this API as part of a multi-turn assistant by registering this function.

Function Contract (OpenAI / Bedrock Format) { "name": "invoke_call_analysis_api", "description": "Invoke the call analysis API to transcribe, analyze, and generate compliance reports for a call based on natural language instructions.", "parameters": { "type": "object", "properties": { "INPUT_TEXT": { "type": "string", "description": "Natural language instruction to perform, e.g. 'Transcribe the call s3://bucket/call.wav' or 'Compliance report for call ID abc123'." }, "SESSION_ID": { "type": "string", "description": "Session ID used to maintain conversation context across requests." } }, "required": ["INPUT_TEXT", "SESSION_ID"] } }

Use this contract with: • OpenAI GPT function calling • Amazon Bedrock Agents with REST API integrations

Rate Limiting (Default) Limit Type Value Rate 5 requests/second Burst 2 concurrent bursts Daily Quota 10,000 requests If exceeded, the API responds with: { "message": "Too Many Requests" } HTTP Status: 429

Common Error Codes Status Meaning Resolution 400 Missing or invalid INPUT_TEXT Ensure both required parameters are sent 403 Missing or invalid API key Add or correct x-api-key 429 Rate limit exceeded Retry with backoff or upgrade plan 500 Server error Internal error or timeout during request

Summary • Use POST /invoke to analyze calls via natural instructions. • Maintain session continuity using SESSION_ID. • Integrate with OpenAI or Bedrock Agents via the provided function contract. • Supports transcription, compliance scoring, and detailed reporting in natural language