How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Purdue HFS Dining Menus API

A public, keyless HTTP API operated by Purdue University Housing and Food Services at api.hfs.purdue.edu, serving dining-court locations, published daily menus by location and date, and per-item nutrition and allergen data. The host is Purdue's own web infrastructure (CNAME wpvwebasp03-01.www.purdue.edu, 128.210.7.106) and the service identifies itself as Purdue.Hfs.Menus.Domain in its own error stack traces, so this is Purdue software on Purdue servers rather than a vendor platform behind a Purdue hostname. HFS publishes no documentation, no OpenAPI, no terms of use and no rate limit; the contract in this repository was written from live probes and is marked generated accordingly.

Purdue HFS Dining Menus API is one of 7 APIs that Purdue University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Campus Life, Dining, Nutrition, Institution-Operated, and Keyless. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and 2 JSON Schemas.

This API exposes 4 operations across 4 paths, organized into 4 resource areas, and defines 9 schemas. It is described by OpenAPI 3.1.0, at version v2.

Requests are made against a single base URL, https://api.hfs.purdue.edu/menus/v2.

4 operations 4 paths 9 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v2
Base URL
https://api.hfs.purdue.edu/menus/v2
Resource Areas
4

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. They span 4 resource areas: Locations, Menus, Items, Media. Each is listed below with its method, path, parameters, and response codes.

Locations 1

Dining courts, quick-bite and on-the-go retail locations.

GET
/locations
List dining locations
listLocations → 200
Menus 1

Published daily menus by location and date.

GET
/locations/{location}/{date}
Get one location's published menu for one date
getLocationMenu 2 params → 200404500
Items 1

Nutrition and allergen detail for a single menu item.

GET
/items/{itemId}
Get nutrition and allergen detail for one menu item
getMenuItem 1 param → 200405
Media 1

Location logo and photo binaries.

GET
/file/{fileId}
Fetch a location logo or photo
getFile 1 param → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Location (11 properties), Meal (8 properties), Address (6 properties), LocationMenu (5 properties). Each schema is shown below with its type and property counts.

LocationsResponse
object
Observed shape of GET /locations.
2 properties
Location
object
11 properties
Address
object
6 properties
LocationMenu
object
5 properties
Meal
object
8 properties
Station
object
2 properties
MenuItem
object
5 properties
Allergen
object
2 properties
MenuItemDetail
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

purdue-hfs-dining-menus-api-openapi.yml Raw ↑

Other APIs Purdue University publishes across the network.

Purdue RCAC API
PURR OAI-PMH Metadata API
Purdue Shibboleth Identity Provider
Purdue e-Pubs OAI-PMH (bepress Digital Commons tenant)
Purdue Events Calendar API (Localist tenant)
Purdue.io Course Catalog API (community-built, third-party)
Where this information came from

This is an independent, third-party profile of Purdue HFS Dining Menus API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.