The pre-ingest/ingest module of Yareta: deposit, validate and submit research data, reserve a DOI, and submit a SIP for archiving. Runs on UNIGE's own host ingest.yareta.unige.ch. Fully bearer-gated — no anonymous operation was reachable on 2026-09-01, and the origin contract at /v3/api-docs returned 401. DOIs minted here resolve under prefix 10.26037, delegated to the DataCite repository account ethz.genfyareta ("Uni Genf: Yareta").
Yareta Ingest 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 3 JSON Schema definitions.
Tagged areas include Ingest, Research Data, Deposit, and DOI. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, and 3 JSON Schemas.
This API exposes
139 operations
across 95 paths,
and defines 60 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.
139 operations95 paths60 schemas22 DELETE63 GET10 PATCH44 POST
Metadata
The identity and technical contract details declared by the specification.
Yareta Ingest 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 139
Across 95 paths, the API surfaces 139 operations — 22 DELETE, 63 GET, 10 PATCH, 44 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 60 schemas that model the data the API accepts and returns. The most detailed are Deposit (46 properties), ArchivalInfoPackage (33 properties), DepositDataFile (24 properties), SipDataFile (24 properties). Each schema is shown below with its type and property counts.
SearchCriteria
object
6 properties
ChangeInfo
object
The change information of an action.
3 properties
RestCollectionSubmissionAgreement
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
RestCollectionSubjectArea
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
MetadataType
object
The metadata type allow to define custom metadata.
11 properties
Language
object
The language for internationalization (i18n) & localization (L10n)
8 properties
ArchivalInfoPackage
object
Archival Information Package (AIP)
33 properties
EmbargoInfo
object
Embargo information.
3 properties
SipDataFile
object
24 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
StatusHistory
object
5 properties
FileList
object
2 properties
LicenseLogo
object
7 properties
License
object
A license represents software licenses (Academic Free License 3.0, Design Science License, MIT License…).
18 properties
RestCollectionDepositDataFile
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
ArchiveType
object
Archive type based on DataCite notion.
7 properties
StreamingResponseBody
Contributor
object
Contributors are people who are involved in archives.
11 properties
Tool
object
Software tool information.
4 properties
LanguageDTO
object
4 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
RestCollectionLicense
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
SubjectArea
object
A subject area delineates a range of academic, administrative, and patrimonial disciplines. Each of these disciplines may follow its own classification system,…
9 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
Label
object
2 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
SubmissionPolicy
object
A submission policy is a policy that can be associated to an SIP. It defines whether an SIP can submitted with or without approval and the amount of time it sh…
10 properties
Deposit
object
A deposit is a simple package to prepare a SIP. Deposit status: - APPROVED = Approved deposit. The SIP preparation is in progress. - CANCELEDITINGMETADATA = A…
46 properties
DepositContributorId
Institution
object
An institution represents academic institutions, such as UNIGE and HES-SO.
12 properties
RestCollectionPage
object
4 properties
RestCollectionSubmissionInfoPackage
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
FacetResultValue
object
2 properties
RestCollectionPerson
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
FacetResult
object
3 properties
RestCollectionDeposit
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
SubmissionInfoPackage
object
Submission Information Package (SIP)
20 properties
OrganizationalUnit
object
An organizational unit is a logical entity that represents a research project or laboratory or any other organizational group of researchers. A preservation sp…
17 properties
Cookie
object
1 property
PersonAvatar
object
7 properties
Pageable
object
3 properties
RestCollectionContributor
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
SubmissionAgreementFile
object
7 properties
DepositContributor
object
5 properties
SubmissionAgreement
object
A submission agreement defines the conditions of the submissions.
8 properties
ChecksumCheck
object
Checksum verification information.
2 properties
OrcidToken
object
Personal token allowing to interact with ORCID API.
8 properties
DownloadToken
object
1 property
OrganizationalUnitLogo
object
7 properties
PreservationPolicy
object
A preservation policy defines whether approval is required for an AIP’s disposition as well as how long it should be kept.
10 properties
Link
object
8 properties
InstitutionLogo
object
7 properties
FileFormat
object
File format informations.
7 properties
Module
object
The functional module.
2 properties
RepresentationInfo
object
OAIS Information Package: SIP, AIP or DIP.
16 properties
VirusCheck
object
Virus check information.
3 properties
Links
object
DepositDataFile
object
24 properties
RestCollectionSipDataFile
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
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 Ingest 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.