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 Göttingen Dataverses API

The Dataverses API from University of Göttingen — 37 operation(s) for dataverses.

University of Göttingen Dataverses API is one of 35 APIs that University of Göttingen publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Dataverses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 54 operations across 37 paths. It is described by OpenAPI 3.0.3, at version 6.4.

Requests are made against a single base URL, https://data.goettingen-research-online.de/api.

54 operations 37 paths 0 schemas 7 DELETE20 GET20 POST7 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
6.4
Base URL
https://data.goettingen-research-online.de/oai
Resource Areas
1

Paths & Operations 54

Across 37 paths, the API surfaces 54 operations — 7 DELETE, 20 GET, 20 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Dataverses 54
POST
/dataverses
Dataverses_addRoot → 200
GET
/dataverses/{identifier}
Dataverses_getDataverse 2 params → 200
POST
/dataverses/{identifier}
Dataverses_addDataverse 1 param → 200
DELETE
/dataverses/{identifier}
Dataverses_deleteDataverse 1 param → 200
POST
/dataverses/{identifier}/actions/:publish
Dataverses_publishDataverse 1 param → 200
GET
/dataverses/{identifier}/assignments
Dataverses_listAssignments 1 param → 200
POST
/dataverses/{identifier}/assignments
Dataverses_createAssignment 2 params → 200
DELETE
/dataverses/{identifier}/assignments/{id}
Dataverses_deleteAssignment 2 params → 200
PUT
/dataverses/{identifier}/attribute/{attribute}
Dataverses_updateAttribute 3 params → 200
GET
/dataverses/{identifier}/contents
Dataverses_listContent 1 param → 200
GET
/dataverses/{identifier}/datasetSchema
Dataverses_getDatasetSchema 1 param → 200
POST
/dataverses/{identifier}/datasets
Dataverses_createDataset 2 params body → 200
POST
/dataverses/{identifier}/datasets/:import
Dataverses_importDataset 3 params → 200
POST
/dataverses/{identifier}/datasets/:importddi
Dataverses_importDatasetDdi 3 params → 200
POST
/dataverses/{identifier}/datasets/:startmigration
Dataverses_recreateDataset 1 param body → 200
PUT
/dataverses/{identifier}/defaultContributorRole/{roleAlias}
Dataverses_updateDefaultContributorRole 2 params → 200
GET
/dataverses/{identifier}/facets
Dataverses_listFacets 2 params → 200
POST
/dataverses/{identifier}/facets
Dataverses_setFacets 1 param → 200
GET
/dataverses/{identifier}/featured
Dataverses_getFeaturedDataverses 1 param → 200
POST
/dataverses/{identifier}/featured
Dataverses_setFeaturedDataverses 1 param → 200
DELETE
/dataverses/{identifier}/featured
Dataverses_deleteFeaturedCollections 1 param → 200
GET
/dataverses/{identifier}/groups
Dataverses_listGroups 2 params → 200
POST
/dataverses/{identifier}/groups
Dataverses_createExplicitGroup 1 param → 200
GET
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses_getGroupByOwnerAndAliasInOwner 2 params → 200
PUT
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses_updateGroup 2 params → 200
DELETE
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses_deleteGroup 2 params → 200
POST
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees
Dataverses_addRoleAssingees 2 params body → 200
PUT
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier}
Dataverses_addRoleAssingee 3 params → 200
DELETE
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier}
Dataverses_deleteRoleAssingee 3 params → 200
GET
/dataverses/{identifier}/guestbookResponses
Dataverses_getGuestbookResponsesByDataverse 2 params → 200
GET
/dataverses/{identifier}/inputLevels
Dataverses_getInputLevels 1 param → 200
PUT
/dataverses/{identifier}/inputLevels
Dataverses_updateInputLevels 1 param → 200
GET
/dataverses/{identifier}/links
Dataverses_listLinks 1 param → 200
GET
/dataverses/{identifier}/metadatablockfacets
Dataverses_listMetadataBlockFacets 1 param → 200
POST
/dataverses/{identifier}/metadatablockfacets
Dataverses_setMetadataBlockFacets 1 param body → 200
POST
/dataverses/{identifier}/metadatablockfacets/isRoot
Dataverses_updateMetadataBlockFacetsRoot 1 param body → 200
GET
/dataverses/{identifier}/metadatablocks
Dataverses_listMetadataBlocks 3 params → 200
POST
/dataverses/{identifier}/metadatablocks
Dataverses_setMetadataBlocks 1 param → 200
GET
/dataverses/{identifier}/metadatablocks/:isRoot
Dataverses_getMetadataRoot_legacy 1 param → 200
POST
/dataverses/{identifier}/metadatablocks/:isRoot
Dataverses_setMetadataRoot_legacy 1 param body → 200
GET
/dataverses/{identifier}/metadatablocks/isRoot
Dataverses_getMetadataRoot 1 param → 200
PUT
/dataverses/{identifier}/metadatablocks/isRoot
Dataverses_setMetadataRoot 1 param body → 200
GET
/dataverses/{identifier}/roles
Dataverses_listRoles 1 param → 200
POST
/dataverses/{identifier}/roles
Dataverses_createRole 1 param → 200
GET
/dataverses/{identifier}/storage/quota
Dataverses_getCollectionQuota 1 param → 200
DELETE
/dataverses/{identifier}/storage/quota
Dataverses_deleteCollectionQuota 1 param → 200
POST
/dataverses/{identifier}/storage/quota/{bytesAllocated}
Dataverses_setCollectionQuota 2 params → 200
GET
/dataverses/{identifier}/storage/use
Dataverses_getCollectionStorageUse 1 param → 200
GET
/dataverses/{identifier}/storagesize
Dataverses_getStorageSize 2 params → 200
GET
/dataverses/{identifier}/userPermissions
Dataverses_getUserPermissionsOnDataverse 1 param → 200
POST
/dataverses/{identifier}/validateDatasetJson
Dataverses_validateDatasetJson 1 param body → 200
POST
/dataverses/{id}/move/{targetDataverseAlias}
Dataverses_moveDataverse 3 params → 200
PUT
/dataverses/{linkedDataverseAlias}/link/{linkingDataverseAlias}
Dataverses_linkDataverse 2 params → 200
DELETE
/dataverses/{linkingDataverseId}/deleteLink/{linkedDataverseId}
Dataverses_deleteDataverseLinkingDataverse 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-gottingen-dataverses-api-openapi.yml Raw ↑

Other APIs University of Göttingen publishes across the network.

GRO.data OAI-PMH Metadata
SUB Göttingen IIIF API
SUB Göttingen TextAPI
University of Göttingen Access API
University of Göttingen addFilesToDataset API
University of Göttingen addFileToDataset API
University of Göttingen addGlobusFilesToDataset API
University of Göttingen Admin API
University of Göttingen Batch API
University of Göttingen Builtin Users API
University of Göttingen Datasetfields API
University of Göttingen Datasets API
Where this information came from

This is an independent, third-party profile of University of Göttingen Dataverses 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.