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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
KU Leuven

KU Leuven Dataverses API

The Dataverses API from KU Leuven — 39 operation(s) for dataverses.

Documentation Provider Profile APIs.io OpenAPI GitHub

KU Leuven Dataverses API is one of 56 APIs that KU Leuven publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 59 operations across 39 paths. It is described by OpenAPI 3.2.0, at version 6.7.1.

Requests are made against a single base URL, https://rdr.kuleuven.be/api.

59 operations 39 paths 0 schemas 8 DELETE21 GET21 POST9 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
6.7.1
Base URL
https://rdr.kuleuven.be/api
Resource Areas
1

Paths & Operations 59

Across 39 paths, the API surfaces 59 operations — 8 DELETE, 21 GET, 21 POST, 9 PUT. Each is listed below with its method, path, parameters, and response codes.

Dataverses 59
POST
/dataverses
Dataverses add root
Dataverses_addRoot → 200
PUT
/dataverses/{dataverseId}/featuredItems
Dataverses update featured items
Dataverses_updateFeaturedItems 1 param body → 200
GET
/dataverses/{identifier}
Dataverses get dataverse
Dataverses_getDataverse 3 params → 200
PUT
/dataverses/{identifier}
Dataverses update dataverse
Dataverses_updateDataverse 1 param → 200
POST
/dataverses/{identifier}
Dataverses add dataverse
Dataverses_addDataverse 1 param → 200
DELETE
/dataverses/{identifier}
Dataverses delete dataverse
Dataverses_deleteDataverse 1 param → 200
POST
/dataverses/{identifier}/actions/:publish
Dataverses publish dataverse
Dataverses_publishDataverse 1 param → 200
GET
/dataverses/{identifier}/assignments
Dataverses list assignments
Dataverses_listAssignments 1 param → 200
POST
/dataverses/{identifier}/assignments
Dataverses create assignment
Dataverses_createAssignment 2 params → 200
DELETE
/dataverses/{identifier}/assignments/{id}
Dataverses delete assignment
Dataverses_deleteAssignment 2 params → 200
PUT
/dataverses/{identifier}/attribute/{attribute}
Dataverses update attribute
Dataverses_updateAttribute 3 params → 200
GET
/dataverses/{identifier}/contents
Dataverses list content
Dataverses_listContent 1 param → 200
GET
/dataverses/{identifier}/datasetSchema
Dataverses get dataset schema
Dataverses_getDatasetSchema 1 param → 200
POST
/dataverses/{identifier}/datasets
Dataverses create dataset
Dataverses_createDataset 2 params body → 200
POST
/dataverses/{identifier}/datasets/:import
Dataverses import dataset
Dataverses_importDataset 3 params → 200
POST
/dataverses/{identifier}/datasets/:importddi
Dataverses import dataset ddi
Dataverses_importDatasetDdi 3 params → 200
POST
/dataverses/{identifier}/datasets/:startmigration
Dataverses recreate dataset
Dataverses_recreateDataset 1 param body → 200
PUT
/dataverses/{identifier}/defaultContributorRole/{roleAlias}
Dataverses update default contributor role
Dataverses_updateDefaultContributorRole 2 params → 200
GET
/dataverses/{identifier}/facets
Dataverses list facets
Dataverses_listFacets 2 params → 200
POST
/dataverses/{identifier}/facets
Dataverses set facets
Dataverses_setFacets 1 param → 200
GET
/dataverses/{identifier}/featured
Dataverses get featured dataverses
Dataverses_getFeaturedDataverses 1 param → 200
POST
/dataverses/{identifier}/featured
Dataverses set featured dataverses
Dataverses_setFeaturedDataverses 1 param → 200
DELETE
/dataverses/{identifier}/featured
Dataverses delete featured collections
Dataverses_deleteFeaturedCollections 1 param → 200
GET
/dataverses/{identifier}/featuredItems
Dataverses list featured items
Dataverses_listFeaturedItems 1 param → 200
POST
/dataverses/{identifier}/featuredItems
Dataverses create featured item
Dataverses_createFeaturedItem 1 param body → 200
DELETE
/dataverses/{identifier}/featuredItems
Dataverses delete featured items
Dataverses_deleteFeaturedItems 1 param → 200
GET
/dataverses/{identifier}/groups
Dataverses list groups
Dataverses_listGroups 2 params → 200
POST
/dataverses/{identifier}/groups
Dataverses create explicit group
Dataverses_createExplicitGroup 1 param → 200
GET
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses get group by owner and alias in owner
Dataverses_getGroupByOwnerAndAliasInOwner 2 params → 200
PUT
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses update group
Dataverses_updateGroup 2 params → 200
DELETE
/dataverses/{identifier}/groups/{aliasInOwner}
Dataverses delete group
Dataverses_deleteGroup 2 params → 200
POST
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees
Dataverses add role assingees
Dataverses_addRoleAssingees 2 params body → 200
PUT
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier}
Dataverses add role assingee
Dataverses_addRoleAssingee 3 params → 200
DELETE
/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier}
Dataverses delete role assingee
Dataverses_deleteRoleAssingee 3 params → 200
GET
/dataverses/{identifier}/guestbookResponses
Dataverses get guestbook responses by dataverse
Dataverses_getGuestbookResponsesByDataverse 2 params → 200
GET
/dataverses/{identifier}/inputLevels
Dataverses get input levels
Dataverses_getInputLevels 1 param → 200
PUT
/dataverses/{identifier}/inputLevels
Dataverses update input levels
Dataverses_updateInputLevels 1 param → 200
GET
/dataverses/{identifier}/links
Dataverses list links
Dataverses_listLinks 1 param → 200
GET
/dataverses/{identifier}/metadatablockfacets
Dataverses list metadata block facets
Dataverses_listMetadataBlockFacets 1 param → 200
POST
/dataverses/{identifier}/metadatablockfacets
Dataverses set metadata block facets
Dataverses_setMetadataBlockFacets 1 param body → 200
POST
/dataverses/{identifier}/metadatablockfacets/isRoot
Dataverses update metadata block facets root
Dataverses_updateMetadataBlockFacetsRoot 1 param body → 200
GET
/dataverses/{identifier}/metadatablocks
Dataverses list metadata blocks
Dataverses_listMetadataBlocks 4 params → 200
POST
/dataverses/{identifier}/metadatablocks
Dataverses set metadata blocks
Dataverses_setMetadataBlocks 1 param → 200
GET
/dataverses/{identifier}/metadatablocks/:isRoot
Dataverses get metadata root legacy
Dataverses_getMetadataRoot_legacy 1 param → 200
POST
/dataverses/{identifier}/metadatablocks/:isRoot
Dataverses set metadata root legacy
Dataverses_setMetadataRoot_legacy 1 param body → 200
GET
/dataverses/{identifier}/metadatablocks/isRoot
Dataverses get metadata root
Dataverses_getMetadataRoot 1 param → 200
PUT
/dataverses/{identifier}/metadatablocks/isRoot
Dataverses set metadata root
Dataverses_setMetadataRoot 1 param body → 200
GET
/dataverses/{identifier}/roles
Dataverses list roles
Dataverses_listRoles 1 param → 200
POST
/dataverses/{identifier}/roles
Dataverses create role
Dataverses_createRole 1 param → 200
GET
/dataverses/{identifier}/storage/quota
Dataverses get collection quota
Dataverses_getCollectionQuota 1 param → 200
DELETE
/dataverses/{identifier}/storage/quota
Dataverses delete collection quota
Dataverses_deleteCollectionQuota 1 param → 200
POST
/dataverses/{identifier}/storage/quota/{bytesAllocated}
Dataverses set collection quota
Dataverses_setCollectionQuota 2 params → 200
GET
/dataverses/{identifier}/storage/use
Dataverses get collection storage use
Dataverses_getCollectionStorageUse 1 param → 200
GET
/dataverses/{identifier}/storagesize
Dataverses get storage size
Dataverses_getStorageSize 2 params → 200
GET
/dataverses/{identifier}/userPermissions
Dataverses get user permissions on dataverse
Dataverses_getUserPermissionsOnDataverse 1 param → 200
POST
/dataverses/{identifier}/validateDatasetJson
Dataverses validate dataset json
Dataverses_validateDatasetJson 1 param body → 200
POST
/dataverses/{id}/move/{targetDataverseAlias}
Dataverses move dataverse
Dataverses_moveDataverse 3 params → 200
PUT
/dataverses/{linkedDataverseAlias}/link/{linkingDataverseAlias}
Dataverses link dataverse
Dataverses_linkDataverse 2 params → 200
DELETE
/dataverses/{linkingDataverseId}/deleteLink/{linkedDataverseId}
Dataverses delete dataverse linking dataverse
Dataverses_deleteDataverseLinkingDataverse 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ku-leuven-dataverses-api-openapi.yml Raw ↑

Other APIs KU Leuven publishes across the network.

KU Leuven Person Information API
AE Profile APIs.io
KU Leuven Educational Offering (Onderwijsaanbod) API
AE Profile APIs.io
KU Leuven Organizational Chart (Organigram) API
AE Profile APIs.io
KU Leuven Vacancies (Vacatures) API
AE Profile APIs.io
KU Leuven Individual Timetable (Uurrooster) API
AE Profile APIs.io
KU Leuven Access API
AE Profile APIs.io
KU Leuven Add Files To Dataset API
AE Profile APIs.io
KU Leuven Add File To Dataset API
AE Profile APIs.io
KU Leuven Add Globus Files To Dataset API
AE Profile APIs.io
KU Leuven Admin API
AE Profile APIs.io
KU Leuven Batch API
AE Profile APIs.io
KU Leuven Builtin Users API
AE Profile APIs.io
#Dataverses
← Back to K APIs
API Details
ID
ku-leuven:ku-leuven-dataverses-api
Base URL
https://rdr.kuleuven.be/api
Docs
https://www.kuleuven.be/rdm/en/rdr/api-documentation
Provider
KU Leuven
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ku-leuven-dataverses-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ku-leuven-dataverses-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 KU Leuven 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.