canonical: https://jentic.com/apis/theeventscalendar.com/theeventscalendar

# The Events Calendar REST API

The Events Calendar REST API allows accessing upcoming events information easily and conveniently. The API exposes 30 endpoints secured with apiKey authentication.

## For AI agents

Programmatically listdoc, listroot. Covers 30 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- listDoc
- listRoot
- createRoot
- getRoot
- deleteRoot
- createBySlug
- getBySlug

## Use cases

### Productivity Operations

Use the The Events Calendar REST API to perform productivity operations programmatically. The API provides 30 endpoints covering core functionality including listdoc, listroot, createroot.

Example prompt: Call GET /doc to listdoc

### Automated Categories Management

Automate categories operations by combining multiple The Events Calendar REST API endpoints. Agents can listroot and then createroot in a single workflow.

Example prompt: Call GET /events to listroot, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call The Events Calendar REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'listdoc', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/doc` | listDoc |
| GET | `/events` | listRoot |
| POST | `/events/{id}` | createRoot |
| GET | `/events/{id}` | getRoot |
| DELETE | `/events/{id}` | deleteRoot |
| POST | `/events/by-slug/{slug}` | createBySlug |
| GET | `/events/by-slug/{slug}` | getBySlug |
| DELETE | `/events/by-slug/{slug}` | deleteBySlug |

## Key resources

- **Categories** — Event category management
- **Events** — Event listing, search, and retrieval
- **General** — General endpoints
- **Organizers** — Organizer management and retrieval
- **Tags** — Event tag management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 72 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 18 / 100
- **View full report:** https://jentic.com/apis/theeventscalendar.com/theeventscalendar/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring The Events Calendar REST API by hand means setting up its API-key auth and handling each event endpoint on the tribe/events route yourself. Through Jentic you install once, import The Events Calendar from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Events Calendar puts the event id and slug in the URL path (`/events/{id}`, `/events/by-slug/{slug}`), so a rule can pin your agent to one event. You choose the operations it may call, so destructive ones like deleting an event are not included unless you add them.
- **Credential handling:** Your Events Calendar 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 upcoming events' or 'fetch an event by slug', and Jentic returns the matching Events Calendar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the The Events Calendar REST API use?

The The Events Calendar REST API uses an API key passed in the `X-WP-Nonce` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I listdoc with the The Events Calendar REST API?

Yes. Use the GET /doc endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the The Events Calendar REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I listdoc through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'listdoc'. Jentic returns the matching The Events Calendar REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the The Events Calendar REST API have?

The The Events Calendar REST API exposes 30 endpoints covering categories, events, general operations.

### Can I limit what my agent is allowed to do with The Events Calendar REST API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. Because The Events Calendar puts the event id and slug in the URL path, such as `/events/{id}` and `/events/by-slug/{slug}`, a rule can pin your agent to a single event. You also choose the operations it may call, so a destructive call like DELETE `/events/{id}` stays off the list unless you add it.