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 North Carolina at Chapel Hill Users API

The Users API from University of North Carolina at Chapel Hill — 10 operation(s) for users.

University of North Carolina at Chapel Hill Users 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 User. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 10 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.

11 operations 10 paths 0 schemas 1 DELETE5 GET5 POST

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 11

Across 10 paths, the API surfaces 11 operations — 1 DELETE, 5 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Users 11
GET
/users/:me
Users_getAuthenticatedUserByToken → 200
POST
/users/register
Users_registerOIDCUser → 200
GET
/users/token
Users_getTokenExpirationDate → 200
DELETE
/users/token
Users_deleteToken → 200
POST
/users/token/recreate
Users_recreateToken 1 param → 200
POST
/users/{consumedIdentifier}/mergeIntoUser/{baseIdentifier}
Users_mergeInAuthenticatedUser 2 params → 200
GET
/users/{identifier}/allowedCollections/{permission}
Users_getUserPermittedCollections 2 params → 200
POST
/users/{identifier}/changeIdentifier/{newIdentifier}
Users_changeAuthenticatedUserIdentifier 2 params → 200
POST
/users/{identifier}/removeRoles
Users_removeUserRoles 1 param → 200
GET
/users/{identifier}/traces
Users_getTraces 1 param → 200
GET
/users/{identifier}/traces/{element}
Users_getTracesElement 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-north-carolina-at-chapel-hill-users-api-openapi.yml Raw ↑

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

UNC GIS Open Data Hub
UNC Libraries Digital Collections Repository (box-c)
Facilities SPOTS REST API
University of North Carolina at Chapel Hill Access API
University of North Carolina at Chapel Hill addFilesToDataset API
University of North Carolina at Chapel Hill addFileToDataset API
University of North Carolina at Chapel Hill addGlobusFilesToDataset API
University of North Carolina at Chapel Hill Admin API
University of North Carolina at Chapel Hill Batch API
University of North Carolina at Chapel Hill Builtin Users API
University of North Carolina at Chapel Hill Datasetfields API
University of North Carolina at Chapel Hill Datasets API
Where this information came from

This is an independent, third-party profile of University of North Carolina at Chapel Hill Users 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.