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
University of North Carolina at Chapel Hill

University of North Carolina at Chapel Hill Dataverses API

The Dataverses API from University of North Carolina at Chapel Hill — 40 operation(s) for dataverses.

Documentation Provider Profile APIs.io OpenAPI GitHub

University of North Carolina at Chapel Hill Dataverses API is one of 39 APIs that University of North Carolina at Chapel Hill 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 61 operations across 40 paths. It is described by OpenAPI 3.0.3, at version 6.8.

Requests are made against a single base URL, https://dataverse.unc.edu/api.

61 operations 40 paths 0 schemas 8 DELETE22 GET22 POST9 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
6.8
Base URL
https://dataverse.unc.edu/api
Resource Areas
1

Paths & Operations 61

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

Dataverses 61
POST
/dataverses
Dataverses_addRoot → 200
PUT
/dataverses/{dataverseId}/featuredItems
Dataverses_updateFeaturedItems 1 param body → 200
GET
/dataverses/{identifier}
Dataverses_getDataverse 3 params → 200
PUT
/dataverses/{identifier}
Dataverses_updateDataverse 1 param → 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}/featuredItems
Dataverses_listFeaturedItems 1 param → 200
POST
/dataverses/{identifier}/featuredItems
Dataverses_createFeaturedItem 1 param body → 200
DELETE
/dataverses/{identifier}/featuredItems
Dataverses_deleteFeaturedItems 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 4 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}/templates
Dataverses_getTemplates 1 param → 200
POST
/dataverses/{identifier}/templates
Dataverses_createTemplate 1 param → 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-north-carolina-at-chapel-hill-dataverses-api-openapi.yml Raw ↑

Other APIs University of North Carolina at Chapel Hill publishes across the network.

UNC GIS Open Data Hub
AE Profile APIs.io
UNC Libraries Digital Collections Repository (box-c)
AE Profile APIs.io
Facilities SPOTS REST API
AE Profile APIs.io
University of North Carolina at Chapel Hill Access API
AE Profile APIs.io
University of North Carolina at Chapel Hill addFilesToDataset API
AE Profile APIs.io
University of North Carolina at Chapel Hill addFileToDataset API
AE Profile APIs.io
University of North Carolina at Chapel Hill addGlobusFilesToDataset API
AE Profile APIs.io
University of North Carolina at Chapel Hill Admin API
AE Profile APIs.io
University of North Carolina at Chapel Hill Batch API
AE Profile APIs.io
University of North Carolina at Chapel Hill Builtin Users API
AE Profile APIs.io
University of North Carolina at Chapel Hill Datasetfields API
AE Profile APIs.io
University of North Carolina at Chapel Hill Datasets API
AE Profile APIs.io
#Dataverses
← Back to U APIs
API Details
ID
university-of-north-carolina-at-chapel-hill:university-of-north-carolina-at-chapel-hill-dataverses-api
Base URL
https://dataverse.unc.edu/api
Docs
https://guides.dataverse.org/en/latest/api/
Provider
University of North Carolina at Chapel Hill
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=university-of-north-carolina-at-chapel-hill-dataverses-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/university-of-north-carolina-at-chapel-hill-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 University of North Carolina at Chapel Hill 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.