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

SDR API

Stanford Digital Repository deposit API. First-party OpenAPI 3.0.0 published by SUL-DLSS under Apache 2.0; 7 paths, 8 operations, bearer auth. Servers are sdr-api-{env}.stanford.edu — the production host resolves in public DNS but does not answer a public connection, so the contract is public and the deployment is internal.

SDR 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, Research Data, and Preservation. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 8 operations across 7 paths, organized into 4 resource areas, and defines 4 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 2 base URLs: https://sdr-api-{env}.stanford.edu, https://sdr-api-{env}.stanford.edu.

8 operations 7 paths 4 schemas 2 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Servers
https://sdr-api-{env}.stanford.edu
https://sdr-api-{env}.stanford.edu
Authentication
HTTP Bearer
License
Resource Areas
4

Authentication & Security 1

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

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 2 GET, 4 POST, 2 PUT. They span 4 resource areas: files, jobs, objects, authentication. Each is listed below with its method, path, parameters, and response codes.

files 2

upload binary files

POST
/v1/direct_uploads
Creates a new file resource
→ 200
PUT
/v1/disk/{encoded_token}
Upload the binary file resource Note that the 'contenttype' of the file posted will be set to 'application/octet-stream' if not supplied. Additional values in 'contenttype' after a semicolon will be…
1 param → 200
jobs 1
GET
/v1/background_job_results/{id}
View results of a background job
background_job_results#show 1 param → 200202404
objects 3

Digital Repository Objects

POST
/v1/resources
Creates a new object
objects#create 4 params body → 200
GET
/v1/resources/{id}
Retrieve the object metadata
resources#show 1 param → 200404422500
PUT
/v1/resources/{id}
Update an existing object
objects#update 4 params body → 200
authentication 2

Authenticate the user

POST
/v1/auth/login
Retrieve a JSON web token for subsequent requests
authentication#login body → 200
POST
/v1/auth/proxy
Retrieve a JSON web token for a different user
authentication#proxy 1 param → 200

Schemas 4

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

BackgroundJobResultResponse
object
3 properties
CreateObjectResponse
object
1 property 1 required
ErrorResponse
object
1 property
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stanford-sdr-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
SURI 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 SDR 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.