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

University of Edinburgh Repository API

Service root, communities, collections and discovery for Edinburgh DataShare

University of Edinburgh Repository API is one of 8 APIs that University of Edinburgh publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Repository. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 2 JSON Schemas.

This API exposes 7 operations across 7 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 8.3.

Requests are made against 2 base URLs: https://datashare.ed.ac.uk/server/api, https://era.ed.ac.uk/server/api.

7 operations 7 paths 8 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
8.3
Base URL
https://datashare.ed.ac.uk/server/api
Resource Areas
1

Paths & Operations 7

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

Repository 7

Service root, communities, collections and discovery for Edinburgh DataShare

GET
/
Service root and HAL link index
getRoot → 200
GET
/core/communities
List communities
listCommunities 2 params → 200
GET
/core/collections
List collections
listCollections 2 params → 200
GET
/discover/search/objects
Discovery search across repository objects
searchObjects 3 params → 200
GET
/discover/browses
List configured browse indexes
listBrowses → 200
GET
/core/items
List items (authenticated)
listItems → 401
GET
/core/bitstreams
List bitstreams (authenticated)
listBitstreams → 401

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Community (8 properties), Collection (8 properties), Root (6 properties), Root_2 (6 properties). Each schema is shown below with its type and property counts.

Community
object
DSpace community (observed shape)
8 properties
CollectionPage
object
3 properties
Collection
object
DSpace collection (observed shape)
8 properties
Root
object
DSpace service root (observed shape)
6 properties
Error
object
Spring Boot error envelope (observed)
5 properties
PageMeta
object
4 properties
CommunityPage
object
3 properties
Root_2
object
DSpace service root (observed shape)
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-edinburgh-repository-api-openapi.yml Raw ↑

Other APIs University of Edinburgh publishes across the network.

ELM — Edinburgh Language Models API
University of Edinburgh Shibboleth Identity Provider
Enterprise API Gateway (gated)
Edinburgh Research Explorer (Elsevier Pure) — tenant
DiscoverEd Library Discovery (Ex Libris Primo) — tenant
University of Edinburgh Catalogue API
University of Edinburgh OAI PMH API
Where this information came from

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