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 Geneva OAI-PMH API

OAI-PMH provider information and metadata formats.

University of Geneva OAI-PMH API is one of 5 APIs that University of Geneva publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include OAI-PMH. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 7 JSON Schemas.

This API exposes 22 operations across 11 paths, and defines 30 schemas. It is described by OpenAPI 3.0.3, at version 3.1.7.

Requests are made against 2 base URLs: https://access.yareta.unige.ch, https://ingest.yareta.unige.ch.

22 operations 11 paths 30 schemas 4 DELETE11 GET2 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
3.1.7
Base URL
https://archive-ouverte.unige.ch/oai
Resource Areas
1

Paths & Operations 22

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

OAI-PMH 22

OAI-PMH provider information and metadata formats.

GET
/oai-info/oai-sets
oai-info_oai-sets_list 3 params → 200
POST
/oai-info/oai-sets
oai-info_oai-sets_create body → 200
DELETE
/oai-info/oai-sets
oai-info_oai-sets_deleteList body → 200
GET
/oai-info/oai-sets/search
oai-info_oai-sets_search_advancedSearch_get 5 params → 200
POST
/oai-info/oai-sets/search
oai-info_oai-sets_search_advancedSearch_post 4 params body → 200
GET
/oai-info/oai-provider/oai
oai-info_oai-provider_oai_process 8 params → 200
POST
/oai-info/oai-provider/oai
oai-info_oai-provider_oai_processPost body → 200
GET
/oai-info/oai-metadata-prefixes
oai-info_oai-metadata-prefixes_list 3 params → 200
POST
/oai-info/oai-metadata-prefixes
oai-info_oai-metadata-prefixes_create body → 200
DELETE
/oai-info/oai-metadata-prefixes
oai-info_oai-metadata-prefixes_deleteList body → 200
GET
/oai-info/oai-metadata-prefixes/search
oai-info_oai-metadata-prefixes_search_advancedSearch_get 5 params → 200
POST
/oai-info/oai-metadata-prefixes/search
oai-info_oai-metadata-prefixes_search_advancedSearch_post 4 params body → 200
GET
/oai-info/oai-sets/{id}
oai-info_oai-sets_by_id_get 1 param → 200
DELETE
/oai-info/oai-sets/{id}
oai-info_oai-sets_by_id_delete 1 param → 200
PATCH
/oai-info/oai-sets/{id}
oai-info_oai-sets_by_id_update 1 param body → 200
GET
/oai-info/oai-metadata-prefixes/{id}
oai-info_oai-metadata-prefixes_by_id_get 1 param → 200
DELETE
/oai-info/oai-metadata-prefixes/{id}
oai-info_oai-metadata-prefixes_by_id_delete 1 param → 200
PATCH
/oai-info/oai-metadata-prefixes/{id}
oai-info_oai-metadata-prefixes_by_id_update 1 param body → 200
GET
/oai-info
oai-info_home → 200
GET
/oai-info/oai-provider
oai-info_oai-provider_status → 200
GET
/oai-info/oai-provider/oai/xsl
oai-info_oai-provider_oai_xsl 1 param → 200
GET
/oai-info/oai-provider/oai/schema
oai-info_oai-provider_oai_schema_xsd → 200

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are OAIMetadataPrefix (14 properties), MetadataType (11 properties), OAIPMHtype (9 properties), IdentifyType (9 properties). Each schema is shown below with its type and property counts.

GetRecordType
object
1 property
Module
object
The functional module.
2 properties
MetadataType
object
The metadata type allow to define custom metadata.
11 properties
RestCollectionOAISet
object
The structure of the REST response: - data: the list of objects - page: the pagination information - links: the HATEOAS links - facets: the search information
4 properties
ChangeInfo
object
The change information of an action.
3 properties
OAIPMHerrorType
object
2 properties
DescriptionType
object
1 property
RecordType
object
3 properties
ResumptionTokenType
object
4 properties
SetType
object
3 properties
ListRecordsType
object
2 properties
OAIMetadataPrefix
object
The OAI metadata prefixes defined the metadata formats supported by OAI-PMH provider. The default metadata prefix is oaidc, derived from Dublin Core.
14 properties
RequestType
object
8 properties
MetadataFormatType
object
3 properties
ListSetsType
object
2 properties
OAIPMHtype
object
9 properties
IdentifyType
object
9 properties
ListMetadataFormatsType
object
1 property
OAISet
object
OAI set.
9 properties
HeaderType
object
4 properties
RestCollectionPage
object
4 properties
AboutType
object
1 property
ListIdentifiersType
object
2 properties
MultiValueMapStringString
object
2 properties
Link
object
8 properties
OAIPMH
object
OAI-PMH Provider Specifications: http://www.openarchives.org/OAI/openarchivesprotocol.html
2 properties
RestCollectionOAIMetadataPrefix
object
The structure of the REST response: - data: the list of objects - page: the pagination information - links: the HATEOAS links - facets: the search information
4 properties
Links
object
FacetResultValue
object
2 properties
FacetResult
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-geneva-oai-pmh-api-openapi.yml Raw ↑

Other APIs University of Geneva publishes across the network.

Archive ouverte UNIGE OAI-PMH
Terminus Protein Prediction API
University of Geneva Access API
University of Geneva Ingest API
Where this information came from

This is an independent, third-party profile of University of Geneva OAI-PMH 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.