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

Stanford University Integrations API

Integrations with other Systems

Stanford University Integrations API is one of 26 APIs that Stanford University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Integration. The published artifact set on APIs.io includes an OpenAPI specification and 5 JSON Schemas.

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

Requests are made against 3 base URLs: https://dor-services-{env}.stanford.edu, https://dor-services-{env}.stanford.edu, https://dor-services-{env}.stanford.edu.

3 operations 3 paths 2 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://purl.stanford.edu
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Stanford University Integrations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 3

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

integrations 3

Integrations with other Systems

POST
/v1/objects/{id}/reindex
Reindex the object in Solr
objects#reindex 1 param → 204
POST
/v1/objects/{id}/indexable
Validate the object for indexing in Solr without actually indexing it
objects#indexable 1 param body → 204422500
POST
/v1/objects/{id}/refresh_metadata
Update object metadata with marc from Symphony
metadata_refresh#refresh_metadata 1 param → 200400422500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Error (4 properties), ErrorResponse (1 property). Each schema is shown below with its type and property counts.

ErrorResponse
object
1 property
Error
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stanford-integrations-api-openapi.yml Raw ↑

Other APIs Stanford University publishes across the network.

Stanford Libraries PURL API
Stanford Libraries IIIF API
Stanford Libraries Library Hours API
Stanford Libraries Digital Stacks API
Stanford Libraries Embed API
ExploreCourses course-data XML query interface
Stanford Identity Provider — SAML 2.0 metadata
Stanford AI API Gateway
MaIS Registry APIs
CAP / Stanford Profiles API
Stanford University About API
Stanford University Authentication API
Where this information came from

This is an independent, third-party profile of Stanford University Integrations 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.