Veritus

Veritus Interactions API

The Interactions API from Veritus — 1 operation(s) for interactions.

Documentation GitHub OpenAPI

Operations 1

POST /interactions/{interactionId}/analyze

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/veritus-interactions-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Veritus Interactions API
  description: API for the Veritus Agent Platform
  license:
    name: MIT
  version: 1.0.0
servers:
- url: https://sandbox.veritus.com/api/v1
security:
- bearerAuth: []
tags:
- name: Interactions
paths:
  /interactions/{interactionId}/analyze:
    post:
      description: Run on-demand analysis on an interaction to extract outcome variables. Supports SMS, voice, and email channels. Analysis is idempotent — if the interaction has already been analyzed, the existing results are returned.
      parameters:
      - name: interactionId
        in: path
        required: true
        description: The unique identifier of the interaction to analyze.
        schema:
          type: string
          format: uuid
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AnalyzeInteractionRequest'
      responses:
        '200':
          description: Analysis completed successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AnalyzeInteractionResponse'
              example:
                requestId: 96b887fb-9371-4515-b51e-28434f58dd7e
                success: true
                data:
                  interactionId: 550e8400-e29b-41d4-a716-446655440000
                  channel: sms
                  outputVariables:
                    stop-requests: false
                    human-follow-up-requested: true
        '400':
          description: Bad request
          content:
            application/json:
              example:
                requestId: 96b887fb-9371-4515-b51e-28434f58dd7e
                publicFacingMessage: Analysis was skipped.
                success: false
        '401':
          description: Unauthorized
          content:
            application/json:
              example:
                requestId: 96b887fb-9371-4515-b51e-28434f58dd7e
                publicFacingMessage: Unauthorized. Make sure to pass the correct authorization token.
                success: false
        '404':
          description: Interaction not found
          content:
            application/json:
              example:
                requestId: 96b887fb-9371-4515-b51e-28434f58dd7e
                publicFacingMessage: Interaction not found
                success: false
      security:
      - bearerAuth: []
      tags:
      - Interactions
components:
  schemas:
    AnalyzeInteractionRequest:
      type: object
      properties:
        applyOutcomes:
          description: Whether to apply configured outcome actions (tags, escalations) to the customer based on the analysis results.
          type: boolean
          default: true
    AnalyzeInteractionResponse:
      required:
      - requestId
      - success
      - data
      type: object
      properties:
        requestId:
          description: The request identifier.
          type: string
          format: uuid
        success:
          description: Whether the operation completed successfully.
          type: boolean
        data:
          type: object
          properties:
            interactionId:
              description: The ID of the analyzed interaction.
              type: string
              format: uuid
            channel:
              description: The channel of the interaction.
              type: string
              enum:
              - sms
              - voice
              - email
            outputVariables:
              description: The analysis outcome variables extracted from the interaction. The specific fields depend on your organization's analysis configuration.
              type: object
              additionalProperties: true
              nullable: true
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer