Maia-analytics user-events API
The user-events API from Maia-analytics — 1 operation(s) for user-events.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/maia-analytics-user-events-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: MAIA Ah User Events API
description: API for MAIA application (migrated from Firebase)
version: 0.1.0
servers:
- url: https://api.maia-analytics.com
description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: user-events
paths:
/api/v1/users/me/events:
get:
tags:
- user-events
summary: User Events Stream
description: 'Subscribe to the authenticated user''s live event channel via SSE.
Forwards messages on ``user:{user_id}:events`` to the browser via the
per-instance ``UserEventsFanout``. Heartbeat every 15 s. The connection
closes when the client disconnects or the server shuts down; the FE
reconnects with jittered backoff and re-fetches snapshot state on each
(re)connect so a dropped event during a disconnect window is recovered
automatically.
No payload is required from the FE — the subscription is implicit in
opening the connection, scoped by the authenticated user.'
operationId: user_events_stream_api_v1_users_me_events_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
security:
- FirebaseAuthMiddleware: []
components:
securitySchemes:
FirebaseAuthMiddleware:
type: http
scheme: bearer