Für Entwickler

Baue mit Votinova

REST-API, Webhooks, Konnektoren und ein MCP-Server. Alles, was die Web-App kann, kann auch die API: Session erstellen, öffnen und die Ergebnisse in unter fünf Minuten in deinem Stack empfangen.

  1. Erstelle einen Zugang in deinem Workspace – zwei Scopes, organisationsweit.
  2. Mach deinen ersten Aufruf: Session per curl erstellen und öffnen.
  3. Abonniere einen Webhook und erhalte die Ergebnisse beim Schließen jeder Frage.
curl -X POST https://api.votinova.prd.atbionapps.com/public/v1/sessions \  -H "X-API-Key: vz_live_…" \  -d '{ "presentation_id": "prs_8f3k2" }' 200 OK   · X-RateLimit-Remaining: 119{  "id": "ses_71xw9",  "join_code": "482913",  "state": "LIVE"}

Jede Oberfläche, ein Vertrag

Jede Integration leitet sich aus demselben OpenAPI-Dokument ab. Ein neuer Endpoint erscheint überall zugleich.

Was damit gebaut wird

Ergebnisse im CRM

Synchronisiere Antworten und Anwesenheit in dein CRM oder Data Warehouse, sobald jede Frage schließt – ein Webhook meldet sich, kein Polling.

Eigenes Reporting

KPIs, Teilnehmer und Ergebnisse über die API mit Cursor-Pagination: Baue den Report genau so, wie deine Organisation ihn will.

Sessions aus deiner Software

Erstelle, öffne und steuere Sessions aus deinem Backend, deinen internen Tools oder deinem Agenten – dieselbe API, die diese Web-App nutzt.

Für Agenten gebaut

Dein Agent kennt Votinova schon

Ein Remote-MCP-Server mit Tools aus dem OpenAPI-Dokument, gefiltert nach den Scopes deines Zugangs. Dazu ein llms.txt, damit jedes Modell die Doku findet.

MCP-Server einrichten
{  "mcpServers": {    "votinova": {      "url": "https://mcp.votinova.com/mcp",      "headers": { "Authorization": "Bearer vz_live_…" }    }  }}

Neueste API-Änderungen

Changelog
  • ADDITIVE

    The plan codes gain STARTER, the tier between FREE and PRO introduced with the 2026-08 pricing. upgrade_to, on a 402 and on a question the caller's plan does not cover, can name it, and so can quota_tiers[].plan_code on GET /public/v1/limits. A client that switches over plan codes needs a branch for STARTER; the other codes keep their meaning and their order.

  • ADDITIVE

    An event stranded by an auto-disable is now dead-lettered, so it can be replayed once the endpoint is back. Recovering from a bad afternoon is supposed to be: the platform pauses the endpoint, you fix it, you re-enable it, you redeliver what never arrived. Redelivery only accepts a dead-lettered delivery, and the queue of an auto-disabled endpoint was being terminated as merely failed — so there was nothing to replay and nothing said so. The arithmetic hid it: a delivery gets 8 attempts and an endpoint is paused after 10 consecutive failures, so a single event in flight always dead-letters first. The counter is per endpoint, and one ordinary session emits three events. Deliveries for an endpoint its owner REMOVED are still terminated without a dead letter: nobody is coming back for those.

  • ADDITIVE

    Three corrections found by driving this API the way an integration does. A bad request body now answers the envelope this surface documents ({ error, code: INVALID_REQUEST_BODY, invalid_fields }) naming the PUBLISHED field: it used to fall through to a shape the API emits nowhere else, which named the internal property (TargetUrl for target_url) and carried no error member for a generated client to read. session.ended is delivered ONCE per close; closing a live session through this API delivered it twice, so anything that posts a summary or books a room did it twice, and the event now always names presentation_id whichever surface closed the session. And enabling an endpoint only revives one the platform paused after failures: it used to undo a DELETE too, so a connector's unsubscribe could be reversed by one call while the connector itself could no longer remove it. Enabling an endpoint that was removed now answers 400 WEBHOOK_NOT_AUTO_DISABLED; register it again instead.

Quota pro Plan

  • STARTER120 Anfragen alle 60 s
  • PRO120 Anfragen alle 60 s
  • TEAM600 Anfragen alle 60 s
  • ENTERPRISE3.000 Anfragen alle 60 s

Deine Quota reist in jeder Antwort mit (X-RateLimit-*-Header).