VISO TRUST API Documentation Guide

Dan Sarlo Updated by Dan Sarlo

Prerequisites

Before you begin, you'll need:

  • An active VISO TRUST account with appropriate permissions
  • An API token (see the authentication section below)
    • We recommend using a service account with access to VISO TRUST to create/own the API Token

REST API Documentation

Our REST API documentation is available through Swagger UI:

URL: https://app.visotrust.com/swagger-ui/index.html

  • You must be logged into the VISO TRUST platform to access the documentation
  • Navigate to the URL above after logging in to explore available endpoints

GraphQL API Documentation

Our GraphQL API documentation is hosted on Apollo Studio:

URL: https://studio.apollographql.com/org/viso-trust/invite/7c558ce0-906f-4a40-8601-7cd1d0f28ddb

Features:

  • Interactive schema explorer
  • Query builder and testing interface
  • Real-time documentation of available queries, mutations, and subscriptions

Getting Your API Token

Before making API calls, you'll need to generate an access token:

📖 Follow our detailed guide 

Important Notes:

  • We recommend using a service account with access to VISO TRUST to create/own the API Token
  • Store your API token securely and never share it publicly
  • Include the token in your API requests as specified in the documentation

Using Your API Token

Once you have your API token, include it in your requests according to the authentication method specified in the API documentation (typically as a Bearer token in the Authorization header).

MCP Server Integration

VISO TRUST provides Model Context Protocol (MCP) server capabilities for enhanced AI integration.

Remote Access

Endpoint: https://mcp.visotrust.com/sse

  • Server-Sent Events (SSE) endpoint is exposed
  • Authentication: Pass your VISO TRUST API token for authentication as a Bearer token in the Authorization header

This documentation is regularly updated. For the most current information, always refer to the live API documentation endpoints provided above.

How did we do?

Contact