Rice Kinder Institute Urban Data Platform API
The only publicly callable API Rice University itself operates. Serves the Kinder Institute for Urban Research's Urban Data Platform: a 431-dataset catalog of Houston and Harris County urban data across fourteen subject categories, with 27 controlled vocabularies, DataCite DOIs under Rice's own 10.25612 prefix, and typed inter-dataset relations drawn from the DataCite RelationType vocabulary. Reads are anonymous and CORS-open; a member-scoped catalog sits behind an undocumented authorizer. Rice publishes no documentation, no OpenAPI and no developer portal for it — the description in this repository was written from live probes on 2026-09-01 and is marked `method: probed`. Operator is institution despite the AWS hostname: the API's own suggestedCitation field names "Rice University-Kinder Institute: UDP", kinder.rice.edu endorses and links the platform, and its DOIs resolve to DataCite client RICE.KINDER under member `rice`.
Rice Kinder Institute Urban Data Platform API is one of 8 APIs that Rice University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Open Data, Urban Research, Research Data, Datasets, and Geospatial. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, API documentation, and 1 JSON Schema.
This API exposes 5 operations across 5 paths, organized into 2 resource areas, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 2026-09-01.
Requests are made against 2 base URLs: https://lg4tooqkr1.execute-api.us-east-1.amazonaws.com/prod, https://5l498ma30i.execute-api.us-east-1.amazonaws.com/dev.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Rice Kinder Institute Urban Data Platform API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (memberSession).
memberSession— Undocumented. Inferred only from the API Gateway authorizer's 401 envelope on /user/catalog. Not verified — no credentials were obtained or used.
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 5 GET. They span 2 resource areas: Datasets, Reference. Each is listed below with its method, path, parameters, and response codes.
The public dataset catalog of the Urban Data Platform.
Controlled vocabularies the catalog's fields draw from.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are DatasetSummary (17 properties), LambdaRuntimeError (4 properties), AuthorizerError (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Rice University 7
Other APIs Rice University publishes across the network.
This is an independent, third-party profile of Rice Kinder Institute Urban Data Platform 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.