Skip to content

Plugin API reference

Base: https://elo-api-prod.quaggamock.com. Responses are JSON. Use the SDK in the browser and temporary grants on the backend. Never substitute Elo cookies, MCP tokens or another provider's keys.

Meeting context

POST /plugin-runtime/{installationId}

Headers: Authorization: Bearer <temporary token> and Content-Type: application/json.

{"operation":"transcript:read","meetingId":"MEETING_ID","cursor":"OPTIONAL_OPAQUE_CURSOR"}

Configuration context

POST /plugin-runtime/{installationId}/config

Accepts a valid configuration or meeting grant for the same installation.

{"operation":"settings:write","value":{"title":"Minutes","includeEvidence":true}}
Operation Input Response
meeting:read meetingId {meeting}
transcript:read meetingId, cursor? {entries, nextCursor}
tags:read meetingId {tags: [{id, name}]}
notes:write meetingId, text (1–8000 chars) {id}
identity:read — {user: {id,name,email}}
settings:read — {settings: {...}}
settings:write value JSON, up to 16 KB {saved: true}

The first endpoint accepts the four meeting operations; /config accepts the three identity/preference operations. notes:write returns {id}, the newly created note ID. transcript:read returns at most 100 ascending entries; nextCursor: null signals completion.

curl --request POST 'https://elo-api-prod.quaggamock.com/plugin-runtime/INSTALLATION_ID' --header "Authorization: Bearer $ELO_PLUGIN_TOKEN" --header 'Content-Type: application/json' --data '{"operation":"meeting:read","meetingId":"MEETING_ID"}'

Download OpenAPI and try the playground. Private dashboard /api/* routes are not a general account API.

Operation reference