ScholarSphere API
Penn State's next-generation institutional repository, written by Penn State University Libraries and released under MIT — not a Figshare, Dataverse or DSpace tenancy. The API is described by the Libraries' own OpenAPI 3.0.2 document with servers set to https://scholarsphere.psu.edu/api/{version}, covering ingest, collections, file upload, featured resources and a public DOI index. Penn State mints its own DataCite DOIs against the service under prefix 10.26207 as repository client psu.scholar. Access is by X_API_KEY header issued by the ScholarSphere team.
ScholarSphere API is one of 9 APIs that Pennsylvania State University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Research Data, Research Repository, Open Access, DOI, and DataCite. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, SDKs, and authentication docs.
This API exposes 7 operations across 7 paths, organized into 6 resource areas, and defines 15 schemas. It is described by OpenAPI 3.0.2, at version 1.0.
Requests are made against a single base URL, https://scholarsphere.psu.edu/api/{version}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
ScholarSphere API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as X_API_KEY (APIKey).
APIKey— Key-based authorization mechanism to the API. A key is obtained fron the ScholarSphere team and is included in the header of all requests.
Paths & Operations 7
Across 7 paths, the API surfaces 7 operations — 2 GET, 4 POST, 1 PUT. They span 6 resource areas: Ingest, Collections, DOIs, Files, Featured Resources, Uploads. Each is listed below with its method, path, parameters, and response codes.
Deposit a new work into ScholarSphere with its metadata, files and permissions.
Create collections that group deposited works.
The public index of DataCite DOIs ScholarSphere knows about (Penn State prefix 10.26207).
Attach or replace files on an existing work.
Promote a resource on the ScholarSphere home page.
Request a presigned destination for a direct file upload.
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are metadata (36 properties), creator (6 properties), ingest (5 properties), errorResponse (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Pennsylvania State University 8
Other APIs Pennsylvania State University publishes across the network.
This is an independent, third-party profile of ScholarSphere 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.