Vermont APIvermont.com ↗
Fetch Vermont community events from vermont.com's calendar. List upcoming events or get full details—venue, address, date, description—via 2 endpoints.
What is the Vermont API?
The Vermont.com API provides access to community event data from vermont.com's public calendar via 2 endpoints. The list_events endpoint returns every upcoming event in calendar order—including title, date, venue, town, and thumbnail—while get_event_by_url fetches the full detail record for a single event, including physical address, event description, start time, and the organizer's external website URL.
curl -X GET 'https://api.parse.bot/scraper/d4c54d4f-a56e-4d88-8198-65b6ca49f363/get_event_by_url?url=https%3A%2F%2Fvermont.com%2Fcalendar%2Fthe-work-in-progress%2F' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace vermont-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Vermont.com Events SDK — bounded, re-runnable; every call capped."""
from parse_apis.vermont_com_api import Vermont, EventNotFound
client = Vermont()
# Browse upcoming events from the calendar (single-page list).
for summary in client.event_summaries.list(limit=5):
print(summary.title, summary.date, summary.town)
# Drill into the first event's full details via summary → detail navigation.
first = client.event_summaries.list(limit=1).first()
if first is not None:
event = first.details()
print(event.title, event.date, event.time)
print(event.venue, event.address)
if event.description:
print(event.description[:120])
# Point lookup by slug — and handle a removed/missing event.
try:
event = client.events.get(url="quilt-exhibition-birthday-party")
print(event.title, event.venue)
except EventNotFound as e:
print("gone:", e.url)
print("exercised: event_summaries.list / EventSummary.details / events.get")
Retrieve full details of a community event from its vermont.com calendar page in one page fetch. Accepts either a full URL (e.g. https://vermont.com/calendar/vermont-brewers-festival/) or just the event slug (e.g. vermont-brewers-festival), as emitted by list_events. Returns title, date, time, venue, address, description, event website link, and featured image when available; fields the page does not show are omitted. A URL for an event that has been removed (past events are taken down) returns a stale_input / input_not_found error.
| Param | Type | Description |
|---|---|---|
| urlrequired | string | Full vermont.com event URL or the event slug; take events[].url or events[].slug from list_events. |
{
"type": "object",
"fields": {
"url": "canonical vermont.com URL for the event",
"date": "event date as displayed (e.g. July 17, 2026)",
"time": "event start time (e.g. 5:30 pm)",
"title": "event name",
"venue": "venue or organizer name",
"address": "physical address from the embedded map",
"image_url": "featured image URL",
"description": "full event description text",
"event_website": "external URL for the event organizer's page"
},
"sample": {
"data": {
"url": "https://vermont.com/calendar/okemo-valley-oktoberfest/",
"date": "October 3, 2026",
"time": "12:00 pm",
"title": "Okemo Valley Oktoberfest",
"venue": "Off The Rails",
"address": "64 Pond Street Ludlow VT 05149",
"image_url": "https://vermont.com/wp-content/uploads/2026/08/ff-a0b81242193258e767a15b5d72f5cecf-ff-Off-The-Rails-Oktoberfest-2026.jpg",
"description": "Join us for our Second Annual Okemo Valley Oktoberfest featuring Craft Beer, Live Music and classic Oktoberfest Food. The event is family and pet friendly and is free to attend.",
"event_website": "https://www.offtherailsvt.com/oktoberfest-2026"
},
"status": "success"
}
}About the Vermont API
What the API Returns
The list_events endpoint returns the complete set of upcoming events currently listed on the vermont.com calendar, ordered soonest first. Each record in the events array includes the event's title, ISO-formatted date, venue, town, summary (as shown on the calendar card, sometimes truncated), image_url, and both a canonical url and a slug for use with the detail endpoint. The top-level count field tells you how many events were returned. The calendar is not paginated, so one call returns all available events—typically around 40–50 at a time.
Event Detail Endpoint
get_event_by_url accepts either a full vermont.com event URL or just the event slug emitted by list_events. It returns the complete detail record: title, date (as displayed, e.g. "July 17, 2026"), time, venue, address (from the embedded map), image_url, description (full body text), and event_website (the organizer's external link). This is the endpoint to use when the summary from list_events is truncated and you need the full event copy.
Coverage and Freshness
All events are Vermont-based community happenings listed on the vermont.com calendar. The data reflects whatever is currently published on that calendar at the time of the request—events that have passed or been removed will no longer appear in list_events. Event detail pages are fetched individually, so freshness for any given event depends on when you call get_event_by_url.
The Vermont API is a managed, monitored endpoint for vermont.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when vermont.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official vermont.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Vermont event digest newsletter using
list_eventsfields: title, date, town, and summary. - Geocode or map Vermont events by extracting the
addressfield fromget_event_by_url. - Filter upcoming Vermont events by town using the
townfield fromlist_events. - Aggregate organizer websites by collecting
event_websiteURLs across all detail records. - Power a Vermont travel itinerary tool by combining event
date,venue, andaddressfields. - Display event thumbnails in a grid UI using the
image_urlfield fromlist_events.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does vermont.com have an official developer API?+
What does `list_events` return versus `get_event_by_url`?+
list_events returns a lightweight summary for every upcoming event on the calendar: title, ISO date, town, venue, slug, summary (often truncated), and thumbnail URL. get_event_by_url takes a URL or slug and returns the full detail record—complete description text, start time, physical address, and the organizer's external website URL. Use list_events to browse and get_event_by_url to fetch the rest.Can I filter events by date range, category, or region within the API?+
list_events returns all upcoming events in the site's default order and filtering must be done client-side using the returned date and town fields. You can fork the API on Parse and revise it to add filtering logic as an additional endpoint.Does the API cover Vermont business listings, lodging, or dining data from vermont.com?+
How current is the event data, and are past events included?+
list_events results. There is no historical archive endpoint; the API only surfaces events the calendar is actively showing.