EPO API

Name: EPO API API
Brand: EPO API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer3 EndpointsREST

For Agents

Authenticate against Event Planon, list managed events, and read the current user's basic details for reporting or directory workflows.

Quickstart

Get started with EPO API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list event planon events"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with EPO API API.

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

GET STARTED

Start building with EPO API API

Explore with Jentic

View OpenAPI Document

Use for: Authenticate against Event Planon and get a bearer token, List all events visible to my Event Planon user, Get the basic profile for the current Event Planon user, Show me the events I manage in Event Planon

Not supported: Does not handle event creation, ticketing, or venue management — use for Event Planon authentication, event listing, and user detail lookup only.

Jentic publishes the only available OpenAPI document for EPO API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use EPO API API for, with concrete tasks.

★ 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.

Authenticate against Event Planon, fetch all events via GetEvents, and post the list to an internal Notion or Confluence page

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.

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.

Search Jentic for 'list event planon events', load the GetEvents operation, and post the result to a Slack channel

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for epo api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Event Planon credentials and bearer tokens are held in the Jentic vault. Agents receive scoped execution tokens, so the raw username, password, and bearer token never enter the model context.

Intent-based discovery

Agents search Jentic for intents like 'list event planon events' and Jentic returns the matching operation with its schema, even though Event Planon does not publish public docs.

Time to first call

Direct integration: 1-2 days because no public spec exists, so endpoints must be reverse-engineered. Through Jentic: under 30 minutes thanks to the Jentic-maintained spec.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cvent API

Enterprise event management with venue sourcing and travel

Choose Cvent when the team needs an end-to-end enterprise event platform rather than a small management surface.

Alternative

Eventleaf API

Event registration and attendance tracking with deeper API surface

Pick Eventleaf when programmatic registration capture and session attendance matter more than directory access.

Complementary

Slack API

Post Event Planon event updates into Slack channels

Use Slack to broadcast event listings and reminders pulled from Event Planon to the relevant teams.

Complementary

Asana API

Track event-related tasks and owners in Asana

Use Asana to manage the operational checklist behind each Event Planon event.

FAQs

Specific to using EPO API API through Jentic.

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 at https://app.jentic.com/sign-up 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.