VOA Health

VOA Health Authentication API

The Authentication API from VOA Health — 1 operation(s) for authentication.

Documentation GitHub OpenAPI

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/voa-health-authentication-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 email required.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.1.0
info:
  title: Voa Integration Identify Authentication API
  version: v1
  description: Exchanges a long-lived Voa Auth Token for a short-lived per-consultation Bearer JWT used to embed the Voa iFrame/plugin and to call the Voa integration APIs (including RNDS). The Auth Token is sent in the `x-voa-token` header; the returned JWT expiration is configurable via the `expiration` field (seconds).
  contact:
    name: Voa integration team
    email: integration@voahealth.com
    url: https://docs.voa.health/integracao/iframe/autenticacao
servers:
- url: https://api.voa.health
  description: Production
tags:
- name: Authentication
paths:
  /integration/identify/:
    post:
      tags:
      - Authentication
      summary: Obter Bearer Token para uma consulta
      description: Returns a secure Bearer JWT for a specific consultation, created from your Auth Token. Each consultation requires its own Bearer token.
      operationId: identify
      security:
      - authToken: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - consultation_id
              - doctor_id
              - patient_id
              properties:
                consultation_id:
                  type: string
                  description: Identificador da consulta.
                doctor_id:
                  type: string
                  description: Identificador do médico.
                patient_id:
                  type: string
                  description: Identificador do paciente.
                expiration:
                  type: integer
                  description: Validade do token em segundos.
                  example: 43200
      responses:
        '200':
          description: Bearer token emitido
          content:
            application/json:
              schema:
                type: object
                properties:
                  token:
                    type: string
                    description: Bearer JWT.
components:
  securitySchemes:
    authToken:
      type: apiKey
      in: header
      name: x-voa-token
      description: Voa Auth Token issued to the integrating partner.
x-provenance:
  generated: '2026-07-21'
  method: derived
  source: Derived faithfully from https://docs.voa.health/integracao/iframe/autenticacao.md (the production Bearer-token exchange endpoint, request headers and body, and response quoted verbatim from the docs). No published OpenAPI was found.