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 Chicago Gen3 Fence — admin/user API

The admin/user API from University of Chicago — 4 operation(s) for admin/user.

University of Chicago Gen3 Fence — admin/user API is one of 44 APIs that University of Chicago publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

Requests are made against a single base URL, https://gen3.datacommons.io/.

4 operations 4 paths 2 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://gen3.datacommons.io/
Authentication
OAuth 2.0
License
Terms of Service
Resource Areas
1

Authentication & Security 1

University of Chicago Gen3 Fence — admin/user API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 1 scope.

Paths & Operations 4

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

admin/user 4
GET
/admin/user/{username}
Return info about a given user
getUserInfo 1 param → 200404
DELETE
/admin/user/{username}/soft
Soft-delete user
softDeleteUser 1 param → 204404
POST
/admin/user/{username}/reactivate
Reactivate a soft-deleted user
reactivateUser 1 param → 200400
POST
/admin/user
Add a new user
createUser body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are UserInfo (22 properties), NewUser (6 properties). Each schema is shown below with its type and property counts.

NewUser
object
6 properties 2 required
UserInfo
object
22 properties 16 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-chicago-admin-user-api-openapi.yml Raw ↑

Other APIs University of Chicago publishes across the network.

University of Chicago Shibboleth Identity Provider — InCommon SAML Metadata
Knowledge@UChicago Repository REST API
Knowledge@UChicago OAI-PMH Endpoint
OCHRE Data Service API
University of Chicago Library IIIF Presentation API
University of Chicago Library IIIF Image API
University of Chicago Library Catalog API (VuFind)
University of Chicago Gen3 indexd — alias API
University of Chicago Gen3 indexd — bulk API
University of Chicago Gen3 indexd — bundle API
University of Chicago Gen3 Peregrine — core metadata API
University of Chicago Gen3 Fence — credentials/api API
Where this information came from

This is an independent, third-party profile of University of Chicago Gen3 Fence — admin/user 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.