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 Chile

University of Chile Dataverses API

The Dataverses API from University of Chile — 28 operation(s) for dataverses.

Documentation Provider Profile APIs.io OpenAPI GitHub

University of Chile Dataverses API is one of 25 APIs that University of Chile 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 41 operations across 28 paths, and defines 3 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against a single base URL, https://datos.uchile.cl.

41 operations 28 paths 3 schemas 5 DELETE14 GET17 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://datos.uchile.cl/api
Resource Areas
1

Paths & Operations 41

Across 28 paths, the API surfaces 41 operations — 5 DELETE, 14 GET, 17 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Dataverses 41
POST
/api/v1/dataverses
addRoot body → default
POST
/api/v1/dataverses/{identifier}
addDataverse 1 param body → default
DELETE
/api/v1/dataverses/{identifier}
deleteDataverse 1 param → default
GET
/api/v1/dataverses/{identifier}
viewDataverse 1 param → default
POST
/api/v1/dataverses/{identifier}/actions/:publish
publishDataverse 1 param → default
POST
/api/v1/dataverses/{identifier}/assignments
createAssignment 2 params body → default
GET
/api/v1/dataverses/{identifier}/assignments
listAssignments 1 param → default
DELETE
/api/v1/dataverses/{identifier}/assignments/{id}
deleteAssignment 2 params → default
GET
/api/v1/dataverses/{identifier}/contents
listContent 1 param → default
POST
/api/v1/dataverses/{identifier}/datasets
createDatasetFromJsonLd 1 param → default
POST
/api/v1/dataverses/{identifier}/datasets/:import
importDataset 3 params body → default
POST
/api/v1/dataverses/{identifier}/datasets/:importddi
importDatasetDdi 3 params body → default
POST
/api/v1/dataverses/{identifier}/datasets/:startmigration
recreateDataset 1 param → default
PUT
/api/v1/dataverses/{identifier}/defaultContributorRole/{roleAlias}
updateDefaultContributorRole 2 params → default
POST
/api/v1/dataverses/{identifier}/facets
setFacets 1 param body → default
GET
/api/v1/dataverses/{identifier}/facets
listFacets 1 param → default
POST
/api/v1/dataverses/{identifier}/groups
createExplicitGroup 1 param body → default
GET
/api/v1/dataverses/{identifier}/groups
listGroups 2 params → default
PUT
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}
updateGroup 2 params body → default
DELETE
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}
deleteGroup 2 params → default
GET
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}
getGroupByOwnerAndAliasInOwner 2 params → default
POST
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees
addRoleAssingees 2 params body → default
PUT
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier: .*}
addRoleAssingee 3 params → default
DELETE
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}/roleAssignees/{roleAssigneeIdentifier: .*}
deleteRoleAssingee 3 params → default
GET
/api/v1/dataverses/{identifier}/guestbookResponses
getGuestbookResponsesByDataverse 2 params → default
GET
/api/v1/dataverses/{identifier}/links
listLinks 1 param → default
POST
/api/v1/dataverses/{identifier}/metadatablockfacets
setMetadataBlockFacets 1 param body → default
GET
/api/v1/dataverses/{identifier}/metadatablockfacets
listMetadataBlockFacets 1 param → default
POST
/api/v1/dataverses/{identifier}/metadatablockfacets/isRoot
updateMetadataBlockFacetsRoot 1 param body → default
POST
/api/v1/dataverses/{identifier}/metadatablocks
setMetadataBlocks 1 param body → default
GET
/api/v1/dataverses/{identifier}/metadatablocks
listMetadataBlocks 1 param → default
POST
/api/v1/dataverses/{identifier}/metadatablocks/:isRoot
setMetadataRoot_legacy 1 param → default
GET
/api/v1/dataverses/{identifier}/metadatablocks/:isRoot
getMetadataRoot_legacy 1 param → default
PUT
/api/v1/dataverses/{identifier}/metadatablocks/isRoot
setMetadataRoot 1 param → default
GET
/api/v1/dataverses/{identifier}/metadatablocks/isRoot
getMetadataRoot 1 param → default
POST
/api/v1/dataverses/{identifier}/roles
createRole 1 param body → default
GET
/api/v1/dataverses/{identifier}/roles
listRoles 1 param → default
GET
/api/v1/dataverses/{identifier}/storagesize
getStorageSize 2 params → default
POST
/api/v1/dataverses/{id}/move/{targetDataverseAlias}
moveDataverse 3 params → default
PUT
/api/v1/dataverses/{linkedDataverseAlias}/link/{linkingDataverseAlias}
linkDataverse 2 params → default
DELETE
/api/v1/dataverses/{linkingDataverseId}/deleteLink/{linkedDataverseId}
deleteDataverseLinkingDataverse 2 params → default

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are RoleDTO (5 properties), ExplicitGroupDTO (3 properties), RoleAssignmentDTO (2 properties). Each schema is shown below with its type and property counts.

RoleDTO
object
5 properties
RoleAssignmentDTO
object
2 properties
ExplicitGroupDTO
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs University of Chile publishes across the network.

Repositorio Academico OAI-PMH
AE Profile APIs.io
University of Chile Access API
AE Profile APIs.io
University of Chile Admin API
AE Profile APIs.io
University of Chile Batch API
AE Profile APIs.io
University of Chile Builtin Users API
AE Profile APIs.io
University of Chile Datasets API
AE Profile APIs.io
University of Chile Datatags API
AE Profile APIs.io
University of Chile Edit API
AE Profile APIs.io
University of Chile Files API
AE Profile APIs.io
University of Chile Harvest API
AE Profile APIs.io
University of Chile Inbox API
AE Profile APIs.io
University of Chile Info API
AE Profile APIs.io
#Dataverses
← Back to U APIs
API Details
ID
university-of-chile:university-of-chile-dataverses-api
Base URL
https://datos.uchile.cl/api
Docs
https://datos.uchile.cl/
Provider
University of Chile
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-chile-dataverses-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/university-of-chile-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 Chile 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.