Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tecnológico de Monterrey Dataverses API

The Dataverses API from Tecnológico de Monterrey — 26 operation(s) for dataverses.

Tecnológico de Monterrey Dataverses API is one of 25 APIs that Tecnológico de Monterrey 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 38 operations across 26 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://datahub.tec.mx.

38 operations 26 paths 3 schemas 5 DELETE13 GET15 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://datahub.tec.mx/api
Resource Areas
1

Paths & Operations 38

Across 26 paths, the API surfaces 38 operations — 5 DELETE, 13 GET, 15 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.

Dataverses 38
POST
/api/v1/dataverses
addRoot body → default
GET
/api/v1/dataverses/{identifier}
viewDataverse 1 param → default
POST
/api/v1/dataverses/{identifier}
addDataverse 1 param body → default
DELETE
/api/v1/dataverses/{identifier}
deleteDataverse 1 param → default
POST
/api/v1/dataverses/{identifier}/actions/:publish
publishDataverse 1 param → default
GET
/api/v1/dataverses/{identifier}/assignments
listAssignments 1 param → default
POST
/api/v1/dataverses/{identifier}/assignments
createAssignment 2 params body → 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
GET
/api/v1/dataverses/{identifier}/facets
listFacets 1 param → default
POST
/api/v1/dataverses/{identifier}/facets
setFacets 1 param body → default
GET
/api/v1/dataverses/{identifier}/groups
listGroups 2 params → default
POST
/api/v1/dataverses/{identifier}/groups
createExplicitGroup 1 param body → default
GET
/api/v1/dataverses/{identifier}/groups/{aliasInOwner}
getGroupByOwnerAndAliasInOwner 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
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
GET
/api/v1/dataverses/{identifier}/metadatablocks
listMetadataBlocks 1 param → default
POST
/api/v1/dataverses/{identifier}/metadatablocks
setMetadataBlocks 1 param body → default
GET
/api/v1/dataverses/{identifier}/metadatablocks/:isRoot
getMetadataRoot_legacy 1 param → default
POST
/api/v1/dataverses/{identifier}/metadatablocks/:isRoot
setMetadataRoot_legacy 1 param → default
GET
/api/v1/dataverses/{identifier}/metadatablocks/isRoot
getMetadataRoot 1 param → default
PUT
/api/v1/dataverses/{identifier}/metadatablocks/isRoot
setMetadataRoot 1 param → default
GET
/api/v1/dataverses/{identifier}/roles
listRoles 1 param → default
POST
/api/v1/dataverses/{identifier}/roles
createRole 1 param body → 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.

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tecnologico-de-monterrey-dataverses-api-openapi.yml Raw ↑

Other APIs Tecnológico de Monterrey publishes across the network.

Tec de Monterrey Dataverse OAI-PMH Endpoint
RITEC Institutional Repository OAI-PMH (DSpace)
Tec de Monterrey API Developer Portal (Institutional APIs)
Tecnológico de Monterrey Access API
Tecnológico de Monterrey Admin API
Tecnológico de Monterrey Batch API
Tecnológico de Monterrey Builtin Users API
Tecnológico de Monterrey Datasets API
Tecnológico de Monterrey Datatags API
Tecnológico de Monterrey Edit API
Tecnológico de Monterrey Files API
Tecnológico de Monterrey Harvest API