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

PEAKS (CAES) — Workstations API

The Workstations resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at peaks.ucdavis.edu. 13 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis's own software — source at github.com/ucdavis/Peaks under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.

PEAKS (CAES) — Workstations API is one of 18 APIs that University of California, Davis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Workstations, peaks, and Campus Operations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 13 operations across 13 paths, and defines 27 schemas. It is described by OpenAPI 3.0.1, at version v1.

Requests are made against a single base URL, https://peaks.ucdavis.edu.

13 operations 13 paths 27 schemas 8 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1
Base URL
https://peaks.ucdavis.edu
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

PEAKS (CAES) — Workstations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (ApiKey).

  • ApiKey — API Key Authentication

Paths & Operations 13

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

Workstations 13
GET
/api/{teamName}/workstations/Search
3 params → 200401403
GET
/api/{teamName}/workstations/SearchInSpace
4 params → 200401403
GET
/api/{teamName}/workstations/GetWorkstationsInSpace
3 params → 200401403
GET
/api/{teamName}/workstations/CommonAttributeKeys
2 params → 200401403
GET
/api/{teamName}/workstations/ListAssigned
3 params → 200401403
GET
/api/{teamName}/workstations/List
7 params → 200401403
GET
/api/{teamName}/workstations/Details/{id}
7 params → 200401403
POST
/api/{teamName}/workstations/Create
2 params body → 200401403
POST
/api/{teamName}/workstations/Assign
5 params → 200401403
POST
/api/{teamName}/workstations/Revoke/{id}
3 params → 200401403
POST
/api/{teamName}/workstations/Update
2 params body → 200401403
POST
/api/{teamName}/workstations/Delete/{id}
3 params → 200401403
GET
/api/{teamName}/workstations/GetHistory/{id}
Return history records Defaults to a max of 5 records returned
4 params → 200401403

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are Person (27 properties), History (22 properties), Equipment (20 properties), Space (18 properties). Each schema is shown below with its type and property counts.

KeySerial
object
14 properties 2 required
FinancialOrganization
object
6 properties 3 required
TeamApiCode
object
4 properties 1 required
TeamPermission
object
7 properties 3 required
WorkstationAttribute
object
5 properties
Document
object
17 properties 1 required
AccessAssignment
object
14 properties
Filter
integer
Team
object
13 properties 2 required
GroupPermission
object
5 properties 2 required
EquipmentAttribute
object
5 properties
Access
object
9 properties 1 required
KeySerialAssignment
object
14 properties
Person
object
27 properties 3 required
Space
object
18 properties
KeyXSpace
object
5 properties 2 required
TeamPpsDepartment
object
5 properties 2 required
Workstation
object
14 properties 2 required
Group
object
4 properties 1 required
GroupXTeam
object
5 properties 2 required
History
object
22 properties 1 required
Equipment
object
20 properties 1 required
User
object
9 properties 3 required
Key
object
11 properties 2 required
Role
object
3 properties 1 required
EquipmentAssignment
object
13 properties
WorkstationAssignment
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uc-davis-workstations-api-openapi.yml Raw ↑

Other APIs University of California, Davis publishes across the network.

Aggie Experts API
DAMS API — UC Davis Library Digital Collections
UC Davis Shibboleth Identity Provider (SAML 2.0 / InCommon)
UC Davis Health FHIR R4 endpoint
IET Middleware Web Service APIs
UC Davis Health Systems Integration APIs
CAES ACE API
PEAKS (CAES) — Access API
PEAKS (CAES) — Documents API
PEAKS (CAES) — Equipment API
PEAKS (CAES) — Keys API
PEAKS (CAES) — KeySerials API
Where this information came from

This is an independent, third-party profile of PEAKS (CAES) — Workstations 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.