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

California Institute of Technology Records API

Published research data records, their metadata, files and DOIs.

California Institute of Technology Records API is one of 13 APIs that California Institute of Technology publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Records. 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 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://data.caltech.edu/api.

2 operations 2 paths 6 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://data.caltech.edu/api/records
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.

Records 2

Published research data records, their metadata, files and DOIs.

GET
/records
Search published records
searchRecords 4 params → 200
GET
/records/{id}
Retrieve a single record
getRecord 1 param → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Record (17 properties), RecordMetadata (6 properties), RecordSearchResult (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Record
object
A published CaltechDATA record, in InvenioRDM record shape.
17 properties
RecordMetadata
object
6 properties
Creator
object
2 properties
RecordSearchResult
object
3 properties
PersistentIdentifiers
object
DOI and OAI identifiers. CaltechDATA mints DOIs through DataCite under its own prefix 10.22002 — pids.doi.provider is observed as datacite.
2 properties
Error
object
Observed error body shape, verified on a 404.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

caltech-records-api-openapi.yml Raw ↑

Other APIs California Institute of Technology publishes across the network.

CaltechDATA OAI-PMH
CaltechAUTHORS REST API and OAI-PMH
Caltech Library Feeds
IRSA Virtual Observatory APIs (Caltech/IPAC)
NED Table Access Protocol (Caltech/IPAC)
NASA Exoplanet Archive TAP (Caltech/IPAC)
Caltech Shibboleth Identity Provider (InCommon)
Caltech Library Guides (Springshare tenancy)
EBSCO Link Resolver (Caltech instance)
California Institute of Technology Data Select API
California Institute of Technology Event API
California Institute of Technology Station API
Where this information came from

This is an independent, third-party profile of California Institute of Technology Records 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.