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

# Nolizi Calendar API

The Nolizi Calendar API lets the owner of a Nolizi scheduling account list their event types, find open slots for the next 14 days, book a slot for an attendee, and cancel a booking. Writes are form-encoded and have real side effects: a new booking triggers the normal Nolizi notifications and calendar updates, and a cancellation may notify attendees. The API is in beta and recommends confirming every write by reading back the upcoming bookings list.

## For AI agents

List your Nolizi event types, find available slots for one of them, book a slot for a named attendee, confirm it against upcoming bookings, and cancel a booking by ID.

## Scope

Does not create event types, edit existing bookings, list past bookings, or send email directly. Use for checking availability, booking, and cancelling meetings on an owner's Nolizi calendar only.

## Capabilities

- List the event types owned by the key holder to get the event slug used for availability and booking
- Find available slots for an event type over the next 14 days
- Book a slot for an attendee with event_type, start, end, name, and email, plus optional booker_tz and location_option
- Reconcile a new booking against the list of up to 100 upcoming confirmed bookings
- Cancel an owned booking by its booking_id

## Use cases

### Scheduling assistant agent through Jentic

A scheduling agent handling an email thread searches Jentic for 'find available slots', receives the listAvailableSlots schema, and calls it with an event slug from listEventTypes. After the attendee picks a time, the agent calls createBooking with the slot's start and end plus the attendee's name and email, then reads listUpcomingBookings to confirm the booking ID, event, time, and attendee match before replying.

Example prompt: Call GET /event-types, pick the slug 'intro-call', call GET /slots with event_type='intro-call', then POST /bookings with event_type, start, end, name='Dana Lee', email='dana@example.com', and confirm the result with GET /bookings

### Lead follow-up with offered times

Sales and service teams can reply to inbound leads with real open times instead of a booking link. GET /slots returns availability for one event type across the next 14 days, so an assistant can pick two or three slots and include them in its reply. Slots are not held, so availability is rechecked at booking time.

Example prompt: Call GET /slots with event_type='consultation' and return the first three available start times in the attendee's time zone

### Booking cleanup and cancellations

When a meeting is called off, the owner can cancel it without opening the dashboard. POST `/bookings/{booking_id}/cancel` cancels an owned booking and may notify attendees; repeating the call on an already-cancelled booking returns cancelled true, so a retry is safe to reconcile.

Example prompt: Call GET /bookings to find the booking for 'Dana Lee' on Thursday, then POST `/bookings/{booking_id}/cancel` with that booking_id

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/event-types` | List owned event types |
| GET | `/slots` | Find available slots for an event type |
| POST | `/bookings` | Create a booking |
| GET | `/bookings` | List upcoming confirmed bookings |
| POST | `/bookings/{booking_id}/cancel` | Cancel a booking |

## Key resources

- **Event types** — List the event types owned by the key holder
- **Slots** — Available booking times for one event type over the next 14 days
- **Bookings** — List upcoming confirmed bookings, create a booking, and cancel a booking by booking_id

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 75 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/nolizi.com/nolizi/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 Nolizi by hand means sending a bearer key, form-encoding every write, and building the read-back step that confirms each booking. Through Jentic you install once, import Nolizi from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Nolizi key is owner-scoped with no granular scopes, and booking targets travel in the form body, so a rule is how you narrow it: limit the agent to the operations it needs, such as listing slots and bookings. You choose the operations it may call, so side-effecting ones like creating or cancelling bookings are not included unless you add them.
- **Credential handling:** Your Nolizi 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 'find available slots' or 'book a meeting', and Jentic returns the matching Nolizi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Calendly API** — Scheduling platform API for event types, invitees, and scheduled events
- **Cronofy Calendar API** — Calendar sync and availability across Google, Microsoft, and Apple calendars
- **Nylas API** — Email, calendar, and contacts API for reading the thread where a meeting is requested

## FAQ

### What authentication does the Nolizi Calendar API use?

Per its OpenAPI spec, the Nolizi Calendar API uses a bearer token: the full API key created at `/app/api-keys`, sent in the Authorization header. The spec notes the key is owner-scoped with no granular permission scopes. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it stays out of the agent's prompt.

### Can I book a meeting with the Nolizi Calendar API?

Yes. POST /bookings takes a form-encoded body with event_type, start, end, name, and email, plus optional booker_tz and location_option. Use a slot freshly returned by GET /slots, and confirm the booking by finding it in GET /bookings, because the spec says a 201 alone is not sufficient proof.

### What are the rate limits for the Nolizi Calendar API?

The OpenAPI spec does not specify rate limits. Check https://calendar.nolizi.com or contact hello@nolizi.com for current limits.

### How do I find open slots with the Nolizi Calendar API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add Nolizi from the Jentic API Directory, and store your API key. Your agent searches for 'find available slots', calls GET /event-types to get the event slug, then GET /slots with that slug as event_type. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Nolizi Calendar API?

Yes. A read-only rule that allows GET /event-types, GET /slots, and GET /bookings lets the agent check availability and review the calendar but never book or cancel. Add POST /bookings when you want it to book, and leave the cancel operation out so it cannot remove meetings. Every call is checked against the rule you set.

### Is there a Nolizi MCP server?

You don't need an MCP server to give your agent the Nolizi Calendar API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, finding operations on demand instead of loading tool definitions into its context.

### Can I see past bookings with the Nolizi Calendar API?

No. GET /bookings returns up to 100 upcoming confirmed bookings sorted by start time, and the spec notes there is no pagination, historical filter, or booking-by-ID endpoint.