Eventium.aiAPI
Manage API keys

Programmable Eventium

One contract. Every governed request.

Authenticate, run a real request, inspect the exact schema, and operate Eventium integrations from one focused developer surface.

Open API Playground Manage API Keys Browse reference

Start here

Use the public developer entrypoints

Use this page when you need exact contract details. For higher-level integration onboarding, use the canonical documentation instead.

REST API

Exact schema and live request inspection for direct HTTP integrations.

  • https://api.eventium.ai/api/openapi.json
  • https://api.eventium.ai/api/openapi.yaml
  • Generated clients and typed SDKs

Hosted MCP

Exact transport examples for tool-based agent integrations.

Authentication

Use API keys for servers and Bearer tokens for user-backed sessions

Long-lived application access should use X-Api-Key. Browser-backed user sessions can use Bearer auth. Browser Basic Auth is not the intended public model for api.eventium.ai.

API key

Recommended for servers, CI, agent runtimes, and MCP clients.

curl -sS https://api.eventium.ai/api/health \
  -H "X-Api-Key: EVENTIUM-REPLACE-ME"

Bearer token

Use for signed-in browser sessions and short-lived user-scoped calls.

curl -sS https://api.eventium.ai/api/health \
  -H "Authorization: Bearer YOUR_JWT"

Key management

Create, rotate, revoke, and delete keys from the hosted key management surface.

Open Manage API Keys

MCP

Connect IDEs and agents through the hosted Eventium MCP

MCP uses a stateful protocol lifecycle: initialize, acknowledge initialization, then discover or invoke tools. The browser testing plane performs that lifecycle for you and limits access to approved, identity-scoped memory tools.

MCP transport

curl -i https://mcp.eventium.ai/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-API-Key: EVENTIUM-REPLACE-ME" \
  -d '{"jsonrpc":"2.0","id":"1","method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"eventium-client","version":"1.0"}}}'

Save the returned Mcp-Session-Id, send notifications/initialized, and include both that session ID and MCP-Protocol-Version: 2025-06-18 on later requests. The MCP connection surface handles those details and exposes only approved test operations.

Generic MCP config

{
  "name": "Eventium MCP",
  "transport": "http",
  "url": "https://mcp.eventium.ai/mcp",
  "headers": {
    "X-API-Key": "EVENTIUM-REPLACE-ME"
  }
}

Webhooks

Integrate async delivery without polling

Use webhooks when your application needs lifecycle or delivery notifications from Eventium.

Endpoint management

  • GET /api/webhooks/endpoints
  • POST /api/webhooks/endpoints
  • PATCH /api/webhooks/endpoints/{id}
  • DELETE /api/webhooks/endpoints/{id}

Delivery operations

  • GET /api/webhooks/deliveries
  • POST /api/webhooks/test
  • Inspect status and validate integrations

Event types

  • GET /api/webhooks/events
  • Discover supported event names
  • Use the schema as the contract source

SDKs and clients

Generate clients from the schema and keep integrations aligned

Use the live OpenAPI description as the source of truth for generated clients and typed request models.

OpenAPI

Use the live JSON or YAML schema as the contract source.

  • /api/openapi.json
  • /api/openapi.yaml
  • Works with standard generators

Python guide

Use the Python integration guide for quick-start client examples.

Quick tests

Validate the public integration surface

Use these examples to confirm the live API and MCP transport are responding correctly.

Fetch the OpenAPI schema

curl -sS https://api.eventium.ai/api/openapi.json -o openapi.json
curl -sS https://api.eventium.ai/api/openapi.yaml -o openapi.yaml

Health check

curl -sS https://api.eventium.ai/api/health \
  -H "X-Api-Key: EVENTIUM-REPLACE-ME"

Interactive reference

Current public OpenAPI specification

Inspect request shapes, authenticate with a Bearer token or API key, and run live calls against the current public integration surface.