canonical: https://jentic.com/apis/nowadays.ai/nowadays

# Nowadays Public API

The Nowadays Public API creates and updates corporate event planning requests in a Nowadays organization and reads them back. An event carries its name, candidate cities, date ranges, attendee count, venue type, guestroom block per night by room type, meeting-room and food and beverage requirements, date flexibility, and currency. Updates can also set a budget breakdown by category and a venue decision deadline, and the event's planning status, such as wait_for_proposals, is returned on read. Events are created in the organization the API key belongs to, and the key's user becomes the owner.

## For AI agents

Create a corporate event request with dates, cities, headcount, room block, and meeting-room needs in Nowadays, update its planning details and budget, and check its planning status.

## Scope

Does not sell tickets, register attendees, book flights, or return venue proposals. Use for creating, updating, and reading corporate event planning requests only.

## Capabilities

- Create an event request with candidate cities in formattedLocations, eventDates ranges, and numPeople
- Specify a guestroom block per night with room-type counts such as Single and Double in accommodations
- Describe meeting-room needs with meetingRoomRequirements for the general session and breakouts
- Update planning details such as budgetBreakdown, decisionDeadline, and flexibility without resending the whole event
- List the organization's events newest first with page and limit pagination
- Read one event's detail, including its planning status, venue type, and currency

## Use cases

### AI assistant that files event requests

An operations assistant turns a chat request such as 'plan a three-day summit for 120 people in Austin or Denver' into a structured planning brief. Through Jentic the agent searches for 'create a corporate event request', gets the Nowadays create operation with its input schema, and sends the required name plus formattedLocations, eventDates, numPeople, and numHotelRoomsNeeded. The response returns the event's public id, which the agent keeps for later updates.

Example prompt: Call POST `/v1/events` with name 'Annual Summit', formattedLocations for Austin and Denver, eventDates 2027-03-15 to 2027-03-17, numPeople 120, and numHotelRoomsNeeded 60, then return the created id

### Room block and meeting space specification

Hotel proposals depend on accurate room nights and meeting space. The Nowadays create operation accepts accommodations as one entry per night with the room-type split, and meetingRoomRequirements describes the general session and the number of breakouts. foodBeverageRequirements and flexibility carry the free-text needs that venues read when they respond.

Example prompt: Call POST `/v1/events` with name 'Sales Kickoff', accommodations of 60 Single and 11 Double for 2027-03-15, meetingRoomRequirements with a general session and 3 breakouts, and foodBeverageRequirements 'breakfast and lunch daily'

### Keeping an event's plan current

Plans change after the first brief: headcount grows, budgets firm up, and a decision date is set. PATCH `/v1/events/{id}` changes only the fields sent, an explicit null clears a field, and if any field is rejected nothing is written. Budget goes in budgetBreakdown keyed by category such as venue, fb, and av.

Example prompt: Call PATCH `/v1/events/{id}` with numPeople 300, budgetBreakdown venue 120000 and fb 40000, and decisionDeadline 2026-09-01T00:00:00.000Z, then call GET `/v1/events/{id}` to confirm the change

### Event pipeline status report

A planner wants a weekly summary of every event in flight. GET `/v1/events` lists the organization's events newest first with page and limit, returning each event's dates, locations, attendee count, and status, and GET `/v1/events/{id}` adds venue type, guestroom estimate, and notes. Results are scoped to what the key's user can open.

Example prompt: Call GET `/v1/events` with page 1 and limit 20, then report each event's name, dates, numPeople, and status, flagging any whose status is wait_for_proposals

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/events` | Create an event |
| GET | `/v1/events` | List events |
| GET | `/v1/events/{id}` | Get an event |
| PATCH | `/v1/events/{id}` | Update an event's planning details |

## Key resources

- **Events** — Corporate event planning requests with dates, candidate cities, headcount, room block, meeting-room needs, budget, and planning status

## 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:** 55 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 74 / 100
  - AI-Readiness & Agent Experience: 31 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/nowadays.ai/nowadays/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 Nowadays by hand means sending the x-api-key header, shaping nested room-block and meeting-room objects, and handling partial PATCH semantics where null clears a field. Through Jentic you install once, import Nowadays from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Nowadays puts the event id in the URL path (`/v1/events/{id}`), so a rule can pin your agent to the read or update operations for one event. You choose the operations it may call, so creating new events or editing existing ones is not included unless you add it.
- **Credential handling:** Your Nowadays 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 'create a corporate event request' or 'update event budget', and Jentic returns the matching Nowadays operation with its input schema, including fields like accommodations and meetingRoomRequirements, so the agent sends a valid request directly.

## Related APIs

- **Cvent REST APIs** — Event management platform covering registration, attendees, and venues
- **Eventbrite** — Ticketing and registration for public and private events
- **Amadeus Hotel Search** — Search hotel availability and offers by city and dates

## FAQ

### What authentication does the Nowadays Public API use?

Per its OpenAPI spec, the Nowadays Public API authenticates with an API key sent in the x-api-key header. The key belongs to an organization and a user: events you create land in that organization with the key's user as owner, and reads are scoped to what that user can open. Through Jentic the key is held by your own instance and injected at call time.

### Can I update only some fields of an event with the Nowadays Public API?

Yes. PATCH `/v1/events/{id}` leaves omitted fields alone, clears a field when you send an explicit null, and writes nothing if any field is rejected. That makes it safe to send a single change such as a new numPeople or decisionDeadline.

### What are the rate limits for the Nowadays Public API?

The OpenAPI spec does not specify rate limits. Check the Nowadays developer documentation at https://docs.nowadays.ai for current limits.

### What is required to create an event with the Nowadays Public API?

Only name is required by the create schema. Everything else is optional, including formattedLocations, eventDates, numPeople, numHotelRoomsNeeded, accommodations, meetingRoomRequirements, foodBeverageRequirements, and currency, which defaults to USD. The response returns the new event's id and a grantedTo count of memberships given visibility.

### How do I create an event request through Jentic?

Search Jentic for 'create a corporate event request', load the Nowadays create operation, and call POST `/v1/events` with a name and the cities, dates, and headcount you have. Keep the returned id so the agent can update the event later with PATCH `/v1/events/{id}.` To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Nowadays MCP server?

You do not need an MCP server to give your agent Nowadays. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the event operations it needs on demand.

### Can I limit what my agent is allowed to do with the Nowadays Public API?

Yes. For a reporting agent, write a rule that allows only GET `/v1/events` and GET `/v1/events/{id}`, so it can list events and read their status but cannot create or change them. Add POST `/v1/events` later if you want it to file new requests, and the calls it makes are logged for review.