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

Aggie Map Dining Locations API

Read-only GeoJSON feed of Texas A&M campus dining locations with live open/closed state, status message, street address and an occupancy signal, served from the university's own Aggie Map backend. Verified 200 on 2026-09-01 returning 54 features to an anonymous request. Texas A&M publishes no documentation, terms or rate limit for this host: it is an application backend, not an offered product, and availability should be treated as unguaranteed.

Aggie Map Dining Locations API is one of 13 APIs that Texas A&M University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Campus Life, Dining, GeoJSON, and Geospatial. The published artifact set on APIs.io includes an OpenAPI specification, sample payloads, API documentation, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.aggiemap.tamu.edu.

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.aggiemap.tamu.edu
Resource Areas
1

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Dining 2

Campus dining locations and live status.

GET
/dining/locations/geojson
List campus dining locations as GeoJSON
getDiningLocationsGeoJson → 200
GET
/dining/locations
Dining locations (non-GeoJSON form)
getDiningLocations → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are DiningProperties (13 properties), DiningFeature (3 properties), PointGeometry (2 properties), DiningFeatureCollection (2 properties). Each schema is shown below with its type and property counts.

DiningFeatureCollection
object
2 properties 2 required
DiningFeature
object
3 properties 3 required
PointGeometry
object
2 properties 2 required
DiningProperties
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

texas-a-m-university-aggiemap-dining-openapi.yml Raw ↑

Other APIs Texas A&M University publishes across the network.

Texas A&M GeoServices Geocoding API
Campus Micromobility Vehicle Positions API
Texas A&M IT ArcGIS REST Services
OAKTrust Institutional Repository — OAI-PMH
Texas A&M Shibboleth Identity Provider Metadata
InCommon Federation Registration
UIN Services API
Texas A&M Course Catalog (CourseLeaf)
Canvas Learning Management System (tenancy)
DataCite Registrant — Texas A&M Libraries
Crossref Member — Texas A&M University Libraries
ROR Registration
Where this information came from

This is an independent, third-party profile of Aggie Map Dining Locations 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.