Skip to main content

​
API changelog

All notable changes to the Animo public API. Breaking changes are called out explicitly.

​
Unreleased

​
v1.2.0 — 2026-06-16

​
Added

  • API access on all plans, including Free (removed Pro-only USE_API gate)
  • GTM assets for AI agent discovery: decision pages, OpenAPI spec, agent eval battery, event starter template, Cursor skill
  • llms.txt v2 with integration contract summary and Mintlify MCP install instructions
  • app.animo.co/llms.txt redirect to docs
  • OpenAPI at /openapi.json with Mintlify API MCP support (x-mint)

​
Documentation

​
v1.1.0 — 2026-06-08

​
Added

  • GET /api/v1/{company}/event/{organizingEvent}/page — show event page content
  • POST /api/v1/{company}/event/{organizingEvent}/page — create/update event page (supports multipart/form-data for header image upload)
  • GET /api/v1/{company}/event/{organizingEvent}/comms — list email templates
  • GET /api/v1/{company}/event/{organizingEvent}/comms/{template} — show email template
  • PATCH /api/v1/{company}/event/{organizingEvent}/comms/{template} — customize email template
  • DELETE /api/v1/{company}/event/{organizingEvent}/comms/{template} — reset template to default
  • page field on EventResource for organizing event show/update responses
  • for-ai-agents.md — integration guide for AI coding agents (what to orchestrate vs. never rebuild)
  • business-case.md — cost comparison for event organisers (fully managed vs. custom site vs. build-your-own)
  • docs.json and llms.txt — Mintlify site config and AI agent entry point (docs.animo.co)

​
Fixed

  • Form and form field id (sqid) now returned in form API responses

​
v1.0.0 — 2026-06-05

Initial documented release of the Animo API v1.

​
Documentation updates

  • Documented Pro plan requirement and billing URL (/admin/settings/billing).
  • Documented public ticket page URL pattern and qty query parameter.
  • Documented form field types (custom vs common) in endpoints/forms.md.
  • Corrected docs from live integration findings: form ID omission, event slug-on-create behavior, timestamp format, empty-list vs 403 entitlement, Mollie requirement for paid tickets, checkout URL pattern, form delete gap.

​
Available endpoints

  • GET /api/v1/user
  • GET /api/v1/companies
  • GET /api/v1/{company}/activations (list, show)
  • GET|POST /api/v1/{company}/events (list, create, show, update, cohost CRUD)
  • GET|POST /api/v1/{company}/event/{organizingEvent}/page (show, update)
  • GET|PATCH|DELETE /api/v1/{company}/event/{organizingEvent}/comms/{template} (list, show, update, reset)
  • GET|POST|PATCH /api/v1/{company}/event/{organizingEvent}/ticket-types
  • GET|POST|PATCH /api/v1/{company}/event/{organizingEvent}/orders
  • GET|POST|PATCH /api/v1/{company}/forms
  • POST|PATCH|DELETE /api/v1/{company}/webhooks (attach, update, detach)

​
Known limitations

  • No GET endpoints for leads, submissions, or meetings despite registered OAuth scopes.
  • Event delete, ticket type delete, order cancel, and form delete routes are missing or commented out.
  • LeadsController and SubmissionsController are stubs without routes.
  • Event slug is ignored on create (derived from name).
  • orders/create form payload is not yet persisted server-side.
  • OrderResource does not expose a payment/checkout URL.
  • No submission/lead ingest endpoint: activations are read-only (GET only), so a custom-built form cannot POST a submission or lead into Animo. Data of record only enters via Animo-hosted activation forms (delivered out via form-submitted / lead-created webhooks). This blocks the “AI builds a form, posts to an Animo activation” pattern — companion gap to orders/create form persistence.