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

SURI API

Stanford Uniform Resource Identifier service — mints the druids every other SDR surface keys on. First-party OpenAPI 3.0.0, Apache 2.0, 3 paths, 4 operations, and an in-contract `legacy` tag alongside `identifiers`. Servers sul-suri-{env}.stanford.edu are internal.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Digital Repository and Persistent Identifiers. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

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

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

4 operations 3 paths 4 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Servers
https://sul-suri-{env}.stanford.edu
https://sul-suri-{env}.stanford.edu
https://sul-suri-{env}.stanford.edu
License
Resource Areas
1

Paths & Operations 4

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

identifiers 4

Identifier operations

POST
/identifiers
Create a new identifier
identifiers#create 1 param → 201500
GET
/identifiers
List all identifiers
identifiers#index → 200
GET
/identifiers/{id}
Show an identifier
identifiers#show 1 param → 200404
POST
/suri2/namespaces/druid/identifiersdeprecated
Create a new identifier
1 param → 201500

Schemas 4

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

BareDruid
string
Digital Repository Unique Identifier (DRUID) without druid: prefix
ErrorResponse
object
1 property
Error
object
3 properties
Identifier
object
an ID record stored in the database
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stanford-suri-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
DOR Services API
Preservation Catalog HTTP API
Technical Metadata API
ExploreCourses course-data XML query interface
Stanford Identity Provider — SAML 2.0 metadata
Stanford AI API Gateway
Where this information came from

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