The access/accession module of Yareta, the University of Geneva e-Research long-term research-data preservation platform: discover, order and download archives (AIP/DIP). Runs on UNIGE's own host access.yareta.unige.ch with contact yareta-admin@unige.ch. The software is the Swiss DLCM/Solidify stack, a national project UNIGE leads, so the deployment and the data are the institution's. Bearer-gated except GET /default-configuration, which is anonymous and declares the institution's ROR id 01swzsf04, its ORCID OAuth wiring and its Shibboleth header handling. The origin contract at /v3/api-docs returned 401 on 2026-09-01; the OpenAPI held here is a derived conversion and is marked as such.
Yareta Access API is one of 11 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 Access, Research Data, Digital Preservation, and OAIS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, and 7 JSON Schemas.
This API exposes
176 operations
across 131 paths,
and defines 83 schemas.
It is described by OpenAPI 3.2.0, at version 3.1.7.
Requests are made against 2 base URLs: https://access.yareta.unige.ch, https://ingest.yareta.unige.ch.
176 operations131 paths83 schemas20 DELETE115 GET10 PATCH31 POST
Metadata
The identity and technical contract details declared by the specification.
Yareta Access API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (auth).
It accepts HTTP bearer tokens (tokenAuth).
auth — Session bearer token issued by the UNIGE eResearch authorization server after interactive sign-in through SWITCH edu-ID / SWITCHaai (Shibboleth). Every protect…
tokenAuth — Personal / download token bearer credential. The Solidify configuration model exposes solidify.security.downloadToken with a 1440-minute download-token lifetim…
Paths & Operations 176
Across 131 paths, the API surfaces 176 operations — 20 DELETE, 115 GET, 10 PATCH, 31 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 83 schemas that model the data the API accepts and returns. The most detailed are ArchivalInfoPackage (33 properties), DipDataFile (24 properties), AipDataFile (24 properties), User (19 properties). Each schema is shown below with its type and property counts.
ChangeInfo
object
The change information of an action.
3 properties
MultiValueMapStringString
object
2 properties
EmbargoInfo
object
Embargo information.
3 properties
Origin
object
1 property
Tool
object
Software tool information.
4 properties
Sitemapindex
object
2 properties
Result
object
The result is the result of REST action (HTTP POST) with the status: - EXECUTED = the action was executed successfully - NOTEXECUTED = the action failed and th…
5 properties
DataFileChecksum
object
5 properties
TUrl
object
5 properties
RestCollectionOrderArchive
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
RestCollectionAipDataFile
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
DisseminationInfoPackage
object
Dissemination Information Package (DIP)
8 properties
RatingType
object
The rating types is the type of grade for a dataset: Quality or Usefulness.
5 properties
Cookie
object
1 property
PersonAvatar
object
7 properties
ChecksumCheck
object
Checksum verification information.
2 properties
AverageRating
object
3 properties
FileFormat
object
File format informations.
7 properties
AipDataFile
object
24 properties
Module
object
The functional module.
2 properties
User
object
A user represents a user of the platform. A person and roles are associated to it.
19 properties
ArchiveMetadata
object
Public metadata of an archive
5 properties
RestCollectionPage
object
4 properties
LoginInfo
object
Login information
2 properties
OrgUnit
object
A organizational unit is a logical entity which could represent a research project or laboratory or all other organizational group of researchers. This entity…
10 properties
MetadataType
object
The metadata type allow to define custom metadata.
11 properties
Id
object
1 property
StreamingResponseBody
AuthLoginInfo
object
Authentification login information.
2 properties
LanguageDTO
object
4 properties
WebPageLabel
object
3 properties
SystemProperties
object
3 properties
FacetResultValue
object
2 properties
Remote
object
1 property
Orcid
object
9 properties
OrcidToken
object
Personal token allowing to interact with ORCID API.
8 properties
DownloadToken
object
1 property
OrganizationalUnitLogo
object
7 properties
Sse
object
1 property
Email
object
5 properties
SolidifyProperties
object
10 properties
ArchiveStatisticsDto
object
3 properties
GitInfoProperties
object
4 properties
Order
object
Orders allow to prepare archive download (DIP) from the archives (AIP).
19 properties
OrcidWebsite
object
2 properties
RestCollectionDipDataFile
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
RestCollectionOrder
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
Security
object
3 properties
ArchivalInfoPackage
object
Archival Information Package (AIP)
33 properties
ApplicationRole
object
The application role defines the priviledge of the user.
3 properties
Person
object
A person is associated to a user on the platform. It contains information such as the person’s ORCID, institution and organizational units it belongs to.
12 properties
ArchiveUserRating
object
Archive ratings are the grade assigned by an user to an archive.
8 properties
TSitemap
object
3 properties
DipDataFile
object
24 properties
RestCollectionArchivalInfoPackage
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
Urlset
object
2 properties
SearchCondition
object
The search conditions describes the query to search in the indexes.
10 properties
Sitemap
object
3 properties
Debug
object
2 properties
RestCollectionDisseminationInfoPackage
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
Pageable
object
3 properties
DLCMDefaultConfig
object
14 properties
RestCollectionArchiveMetadata
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
Link
object
8 properties
RepresentationInfo
object
OAIS Information Package: SIP, AIP or DIP.
16 properties
Links
object
Message
object
1 property
Commit
object
4 properties
RestCollectionOrgUnit
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
SearchCriteria
object
6 properties
RestCollectionArchiveUserRating
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
StatusHistory
object
5 properties
DisseminationPolicyDto
object
3 properties
StatisticsInfo
object
Archive statistics information.
3 properties
AuthUserDto
object
19 properties
DLCMConfig
object
14 properties
RestCollectionStatusHistory
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
Build
object
4 properties
FacetResult
object
3 properties
CitationDto
object
4 properties
OrderArchive
object
2 properties
OrderSubsetItem
object
5 properties
VirusCheck
object
Virus check information.
3 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Yareta Access 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.