canonical: https://jentic.com/apis/eventplanon.com/eventplanon # Eventplanon EPO API Jentic publishes the only available OpenAPI specification for EPO API, keeping it validated and agent-ready. The Event Planon API exposes a small surface for authenticating a user, listing events, and retrieving basic user details. Three operations cover the developer login flow, the GetEvents call for event listings, and a settings call for user metadata, which is enough to wire Event Planon into reporting tools or an internal events directory. Authentication is via bearer token issued by the Authenticate endpoint. ## For AI agents Authenticate against Event Planon, list managed events, and read the current user's basic details for reporting or directory workflows. ## Scope Does not handle event creation, ticketing, or venue management - use for Event Planon authentication, event listing, and user detail lookup only. ## Capabilities - Authenticate a user and obtain a bearer token via `/api/login/Authenticate` - List the events visible to the authenticated user via `/api/Event/GetEvents` - Read the basic user profile from `/api/Setting/GetUserBasicDetails` - Surface Event Planon event listings inside an internal directory or chat assistant - Power read-only reporting on Event Planon event coverage ## Use cases ### Internal Event Directory Build a single internal page that lists every event the operations team is running in Event Planon, joined to ownership data from the user details endpoint. The GetEvents call returns the canonical list and the user details call provides ownership context. The first version takes a few hours to wire end to end. Example prompt: Authenticate against Event Planon, fetch all events via GetEvents, and post the list to an internal Notion or Confluence page ### Login and Token Health Check Run a scheduled check that exercises the Authenticate endpoint and verifies the resulting bearer token still works against GetEvents, so integration owners are alerted before tokens silently expire. This protects downstream automations against authentication drift. Runs in seconds per check. Example prompt: Call `/api/login/Authenticate` with the service account credentials and verify GetEvents responds 200 with the resulting token ### AI Agent Integration via Jentic Wire an internal assistant to Event Planon through Jentic so staff can ask 'what events are running this quarter?' in chat and have the agent call GetEvents. Jentic's vault holds the Event Planon credentials and Jentic search resolves the natural-language intent to the right operation. Usable inside an hour of connecting the account. Example prompt: Search Jentic for 'list event planon events', load the GetEvents operation, and post the result to a Slack channel ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/login/Authenticate` | Authenticate and return a bearer token | | POST | `/api/Event/GetEvents` | List events for the authenticated user | | POST | `/api/Setting/GetUserBasicDetails` | Get the authenticated user's basic profile | ## Key resources - **Authentication** — Authenticate a user and obtain a bearer token - **Events** — List events visible to the authenticated user - **User Settings** — Read basic user profile details ## Why Jentic - **Setup:** Wiring Event Planon by hand means handling its authenticate-then-bearer flow, pointing at the devapi.eventplanon.com host, and coding the POST-based event and user lookups yourself. Through Jentic you install once, import the EPO API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Event Planon sends its parameters in the request body on POST operations rather than in the URL path, so scope the agent to the operations it needs, such as listing events and reading user basic details, rather than to one record. Every operation you credit the agent with comes from the allowed set you define. - **Credential handling:** Your Event Planon credentials and bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list event planon events' or 'get user basic details', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Cvent API** — Enterprise event management with venue sourcing and travel - **Eventleaf API** — Event registration and attendance tracking with deeper API surface - **Slack API** — Post Event Planon event updates into Slack channels - **Asana API** — Track event-related tasks and owners in Asana ## FAQ ### Why is there no official OpenAPI spec for EPO API? Event Planon does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EPO 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, to start calling Event Planon. ### What authentication does the EPO API use? The EPO API uses bearer token authentication. Tokens are issued by `/api/login/Authenticate` and must be sent on subsequent calls. Through Jentic, the long-lived credentials sit in the encrypted vault and the bearer token is refreshed automatically. ### Can I list events with the EPO API? Yes. POST `/api/Event/GetEvents` returns the events visible to the authenticated user. The response is suited to populating an internal events directory or feeding a chat assistant that answers event questions. ### What are the rate limits for the EPO API? The current OpenAPI spec does not declare rate limits. Event Planon's internal documentation is the source of truth; back off on HTTP 429 and avoid tight polling loops in production code. ### How do I call GetEvents through Jentic? Search Jentic for 'list event planon events', load the POST `/api/Event/GetEvents` operation, and execute it. Install with pip install jentic and use the async search, load, execute pattern. The bearer token refresh is handled by Jentic's credential layer. ### Does the EPO API support creating events? Not in the current Jentic-generated specification. The exposed surface covers authentication, event listing, and user details only. Event creation is performed in the Event Planon platform UI. ### Can I limit what my agent is allowed to do with the Event Planon API? Yes. Because you run Jentic One yourself, your own rules decide which Event Planon operations and credentials the agent may use, and it can call only the operations you grant it. Since Event Planon passes its parameters in the POST request body rather than in the URL path, you scope by operation rather than by record, so you can allow GetEvents and GetUserBasicDetails for read-only reporting while withholding anything else. Every operation the agent can reach comes from the allowed set you define, and the stored credentials are injected only at execution time.