UNL APIunl.edu ↗
Access University of Nebraska-Lincoln events, deadlines, and date-based schedules via 3 endpoints. Filter by event type, keyword, or date.
What is the UNL API?
The UNL API provides 3 endpoints for querying University of Nebraska-Lincoln calendar data, covering events, deadlines, and date-specific schedules. The search_events endpoint accepts a keyword query plus an optional event_type filter and returns full event records with dates, locations, contact details, and calendar origin. The other endpoints narrow results to chronologically ordered deadlines or all events on a specific calendar date.
curl -X GET 'https://api.parse.bot/scraper/44e0e7af-0152-4c4a-8cfa-da7939562cce/search_events?limit=5&query=deadline&event_type=deadline' \ -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 unl-edu-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: UNL Events SDK — search events, list deadlines, browse by date."""
from parse_apis.unl_edu_api import UNLEvents, EventType, ParseError
client = UNLEvents()
# List upcoming deadlines — returns Event instances filtered to deadline type.
for deadline in client.events.list_deadlines(limit=3):
print(deadline.title, deadline.start, deadline.event_types)
# Search events by keyword with a type filter.
for event in client.events.search(query="workshop", event_type=EventType.WORKSHOP, limit=3):
print(event.title, event.start, event.audiences)
# Get events for a specific date — drill into location details.
event = client.events.by_date(date="2026-07-15", limit=1).first()
if event:
print(event.title, event.start, event.end)
if event.location:
print(event.location.name, event.location.city)
# Typed error handling: catch a parse error on an upstream issue.
try:
results = client.events.by_date(date="2099-12-31", limit=1).first()
print("Result:", results)
except ParseError as exc:
print(f"Error: {exc}")
print("exercised: events.list_deadlines / events.search / events.by_date")
Search University of Nebraska-Lincoln events by keyword query and optional event type filter. When no query is provided, returns upcoming events. Results include full event details with dates, locations, contacts, and calendar origin.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of events to return. |
| query | string | Search query to match against event titles and descriptions. When empty, returns upcoming events. |
| event_type | string | Filter by event type. When omitted, all types are returned. |
{
"type": "object",
"fields": {
"query": "string",
"total": "integer",
"events": "array of event objects",
"event_type": "string or null"
},
"sample": {
"data": {
"query": "deadline",
"total": 54,
"events": [
{
"end": "2026-07-10T10:00:00-05:00",
"start": "2026-07-10T10:00:00-05:00",
"title": "Robinette Farm weekly box order",
"status": "Happening As Scheduled",
"all_day": false,
"contacts": [
"Annalisa Davenport"
],
"event_id": "173865",
"location": null,
"subtitle": null,
"audiences": [
"Faculty",
"Staff"
],
"web_pages": [
{
"url": "//events.unl.edu/2026/07/10/199842/",
"title": "Event Instance URL"
}
],
"description": "This event is a standing reminder...",
"event_types": [
"Deadline"
],
"calendar_url": "https://events.unl.edu/healthieru",
"is_recurring": true,
"recurs_until": "2026-10-23 23:59:00",
"calendar_name": "Healthier U",
"short_description": null
}
],
"event_type": null
},
"status": "success"
}
}About the UNL API
What the API Returns
All three endpoints return event objects drawn from the University of Nebraska-Lincoln calendar. A typical event record includes the event title, scheduled dates and times, location, contact information, the originating calendar, and a classified event type. The search_events endpoint returns a query string, a total count, a nullable event_type field, and an events array. When the query parameter is left empty, the endpoint falls back to returning upcoming events ordered by proximity to the current date.
Endpoints and Filtering
search_events accepts a query string to match against event titles and descriptions, an optional event_type string to narrow results to a specific category, and an integer limit to cap the result count. get_events_by_date takes a required date in YYYY-MM-DD format and supports the same event_type and limit parameters, returning every scheduled event on that day. get_deadlines requires no filter parameters beyond an optional limit and returns only events classified as deadlines, ordered chronologically — useful for pulling registration cutoffs, application due dates, and similar time-sensitive items.
Coverage and Scope
The API reflects the public UNL calendar, which covers university-wide academic events, lectures, performances, athletic events, administrative deadlines, and departmental activities. Response fields consistently include location and contact data alongside scheduling details, making it straightforward to build displays that need more than just a title and timestamp. The event_type filter is shared across search_events and get_events_by_date, so type-based filtering behaves consistently regardless of which endpoint you call.
The UNL API is a managed, monitored endpoint for unl.edu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when unl.edu 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 unl.edu 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?+
- Display upcoming UNL events on a student portal filtered by event type such as lectures or performances
- Pull all academic deadlines chronologically via
get_deadlinesto populate a registration reminder tool - Query
get_events_by_dateto build a day-view calendar widget for a specific campus date - Search
search_eventsby keyword to surface relevant events in a campus chatbot or assistant - Aggregate UNL event locations and contacts for a campus map integration
- Monitor new events matching a keyword on a recurring schedule for alerting or digest emails
- Filter events by type across a date range by combining
get_events_by_datecalls with theevent_typeparameter
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does the University of Nebraska-Lincoln have an official public events API?+
What does the `get_deadlines` endpoint return, and how is it different from `search_events`?+
get_deadlines returns only events classified as deadline-type entries from the UNL calendar, ordered chronologically. It accepts only a limit parameter. search_events covers all event types and supports keyword and event_type filtering, so it is broader in scope but not narrowed specifically to deadlines.Can I retrieve events across a date range rather than a single date?+
get_events_by_date targets a single date in YYYY-MM-DD format, and search_events returns upcoming or keyword-matched events without a date-range parameter. You can fork this API on Parse and revise it to add a date-range endpoint.Does the API include event registration links or ticketing information?+
How fresh is the event data, and does the API cover past events?+
get_deadlines and the default search_events response focus on upcoming events. Historical or archived events are not an explicitly supported query pattern — get_events_by_date can be called with a past date, but coverage of older events depends on what the UNL calendar retains.