canonical: https://jentic.com/apis/dandelion.events/dandelion-events # Dandelion Events API Jentic publishes the only available OpenAPI specification for Dandelion Events API, keeping it validated and agent-ready. Dandelion is an event-management platform used by community organisers and ethical event hosts to publish events, accept bookings, and manage followers. The API exposes four read operations covering the authenticated user, organisation events, organisation followers, and ticket orders, designed primarily for Zapier-style integrations and lightweight automation. Authentication uses an API key in the Authorization header. ## For AI agents List Dandelion organisation events, followers, and ticket orders, and read the authenticated organiser profile for downstream automation. ## Scope Does not handle event creation, payment processing, or marketing email delivery - use for reading Dandelion events, followers, and ticket orders only. ## Capabilities - List events published by an authenticated Dandelion organisation - Retrieve followers attached to a Dandelion organisation profile - List ticket orders placed against organisation events - Read the authenticated organiser profile for context-aware automations - Authenticate organiser requests using an API key in the Authorization header ## Use cases ### Calendar and CRM Sync for Event Organisers Mirror Dandelion events and ticket orders into an organiser's calendar or CRM. The GET `/z/organisation_events` and GET `/z/organisation_event_orders` endpoints supply the event metadata and attendee records needed to keep a downstream tool current. Suitable for community organisers, retreat hosts, and small ticketed venues that already use Dandelion as the source of truth. Example prompt: Pull the latest 50 organisation events and their corresponding ticket orders, then create matching entries in the user's calendar and CRM. ### Follower-Based Audience Analytics Analyse who follows an organiser to inform community programming and outreach. The GET `/z/organisation_followers` endpoint returns the follower list for the authenticated organisation, which can be joined with order history to identify repeat attendees. Useful for community-led organisers running recurring gatherings. Example prompt: Fetch the organisation followers list, cross-reference with organisation event orders, and return the followers who have attended at least two events. ### Automated Attendee Communications Trigger downstream messaging when ticket orders are placed by reading orders on a schedule and feeding new entries into a notification flow. The GET `/z/organisation_event_orders` endpoint is well suited to polling-based automations of the kind originally built for Zapier. Helps organisers send personalised confirmations or surveys without manual exports. Example prompt: Poll organisation event orders every 15 minutes, detect new orders since the last run, and trigger a thank-you email to each new attendee. ### Agent Workflows for Ethical Event Operators via Jentic Agents managing event operations for community-led organisers can call Dandelion through Jentic without storing each organiser's API key. The agent searches Jentic for the relevant intent, loads the schema, and pulls events, followers, or orders for inclusion in a workflow. This keeps credentials isolated per organiser. Example prompt: Use Jentic to search 'list dandelion organisation events', load the GET `/z/organisation_events` schema, and return a summary of upcoming events for the organiser. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/z` | Get the authenticated user profile | | GET | `/z/organisation_events` | List organisation events | | GET | `/z/organisation_followers` | List organisation followers | | GET | `/z/organisation_event_orders` | List organisation event ticket orders | ## Key resources - **Events** — List events published by the authenticated organisation - **Followers** — List followers of the authenticated organisation - **Orders** — List ticket orders placed against organisation events - **User** — Read the authenticated organiser profile ## Why Jentic - **Setup:** Wiring Dandelion Events by hand means learning its Authorization header key against dandelion.events and building the read plumbing for events, followers, and orders yourself. Through Jentic you install once, import the Dandelion Events API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Dandelion selects the organiser's records through request parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as listing organisation events or ticket orders. This API is read-only here, so the agent can only fetch what you allow it to fetch. - **Credential handling:** Your Dandelion organiser API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Dandelion organisation events' or 'read ticket orders', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Ticketmaster Discovery API** — Ticketmaster discovery covers large-scale ticketed events; Dandelion targets community-led organisers. - **Airtable API** — Airtable stores attendee and event records; Dandelion supplies the live event and order feed. - **Mailchimp API** — Mailchimp sends follow-up campaigns to attendees Dandelion has captured. ## FAQ ### Why is there no official OpenAPI spec for Dandelion Events API? Dandelion Events does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dandelion Events API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Dandelion Events API use? The Dandelion Events API uses an API key passed in the Authorization header. Through Jentic the organiser key is held in the vault and never enters the agent's context. ### Can I list ticket orders with the Dandelion Events API? Yes. The GET `/z/organisation_event_orders` endpoint returns ticket orders placed against the authenticated organisation's events, suitable for periodic polling and downstream automation. ### What are the rate limits for the Dandelion Events API? The OpenAPI spec does not declare explicit rate limits. Treat the API as polling-friendly but apply backoff on 429 responses, especially when iterating through orders for high-volume organisers. ### How do I sync Dandelion events to another tool through Jentic? Run pip install jentic, then search Jentic for 'list dandelion organisation events', load the GET `/z/organisation_events` schema, and execute it on a schedule to push events into your calendar, CRM, or notification system. ### Does the Dandelion Events API let me create or update events? No. The published spec exposes read-only endpoints for events, followers, orders, and the authenticated user. Event creation and edits remain in the Dandelion web interface. ### Can I limit what my agent is allowed to do with the Dandelion Events API? Yes. Because you run Jentic One yourself, your own rules decide which of the four Dandelion operations the agent may call, so you can allow it to list organisation events or ticket orders while blocking the followers or authenticated-user reads. Since Dandelion selects records through request parameters rather than a resource id in the path, and every operation is read-only, the agent can only fetch the data you permit and can never create or change anything. You also control which organiser API key is available at execution time, keeping each organiser's access isolated.