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) — Equipment API

The Equipment 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. 17 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) — Equipment API is one of 20 APIs that University of California, Davis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 17 operations across 17 paths, and defines 64 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

17 operations 17 paths 64 schemas 11 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

PEAKS (CAES) — Equipment 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 17

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

Equipment 17
GET
/api/{teamName}/equipment/Search
Get api by team name equipment search
getApiByTeamNameEquipmentSearch 3 params → 200401403
GET
/api/{teamName}/equipment/SearchAttributes
Get api by team name equipment search attributes
getApiByTeamNameEquipmentSearchAttributes 3 params → 200401403
GET
/api/{teamName}/equipment/GetEquipmentInSpace
Get api by team name equipment get equipment in space
getApiByTeamNameEquipmentGetEquipmentInSpace 3 params → 200401403
GET
/api/{teamName}/equipment/CommonAttributeKeys
Get api by team name equipment common attribute keys
getApiByTeamNameEquipmentCommonAttributeKeys 2 params → 200401403
GET
/api/{teamName}/equipment/ListEquipmentTypes
Get api by team name equipment list equipment types
getApiByTeamNameEquipmentListEquipmentTypes 2 params → 200401403
GET
/api/{teamName}/equipment/ListAssigned
Get api by team name equipment list assigned
getApiByTeamNameEquipmentListAssigned 3 params → 200401403
GET
/api/{teamName}/equipment/List
List all equipments for a team
getApiByTeamNameEquipmentList 3 params → 200401403
GET
/api/{teamName}/equipment/Details/{id}
Get api by team name equipment details by id
getApiByTeamNameEquipmentDetailsById 4 params → 200401403
POST
/api/{teamName}/equipment/Create
Create api by team name equipment create
postApiByTeamNameEquipmentCreate 2 params body → 200401403
POST
/api/{teamName}/equipment/Duplicate
Create api by team name equipment duplicate
postApiByTeamNameEquipmentDuplicate 2 params body → 200401403
POST
/api/{teamName}/equipment/Assign
Create api by team name equipment assign
postApiByTeamNameEquipmentAssign 5 params → 200401403
POST
/api/{teamName}/equipment/Update
Create api by team name equipment update
postApiByTeamNameEquipmentUpdate 2 params body → 200401403
POST
/api/{teamName}/equipment/Revoke/{id}
Create api by team name equipment revoke by id
postApiByTeamNameEquipmentRevokeById 3 params → 200401403
POST
/api/{teamName}/equipment/Delete/{id}
Create api by team name equipment delete by id
postApiByTeamNameEquipmentDeleteById 3 params → 200401403
GET
/api/{teamName}/equipment/GetHistory/{id}
Takes the top 5 history records
getApiByTeamNameEquipmentGetHistoryById 4 params → 200401403
GET
/api/{teamName}/equipment/GetComputer/{id}
Get api by team name equipment get computer by id
getApiByTeamNameEquipmentGetComputerById 3 params → 200401403
GET
/api/{teamName}/equipment/GetComputersBySearch
Get api by team name equipment get computers by search
getApiByTeamNameEquipmentGetComputersBySearch 3 params → 200401403

Schemas 64

The contract defines 64 schemas that model the data the API accepts and returns. The most detailed are TypeInfo (80 properties), Type (71 properties), MethodInfo (35 properties), ConstructorInfo (32 properties). Each schema is shown below with its type and property counts.

SecurityRuleSet
integer
AccessAssignment
object
14 properties
MethodInfo
object
35 properties
EquipmentAttribute
object
5 properties
Key
object
11 properties 2 required
CustomAttributeData
object
4 properties
Document
object
17 properties 1 required
MethodAttributes
integer
KeySerial
object
14 properties 2 required
WorkstationAttribute
object
5 properties
ParameterAttributes
integer
TeamPpsDepartment
object
5 properties 2 required
MethodImplAttributes
integer
TypeInfo
object
80 properties
User
object
9 properties 3 required
History
object
22 properties 1 required
EquipmentAssignment
object
13 properties
Equipment
object
20 properties 1 required
GroupXTeam
object
5 properties 2 required
FieldAttributes
integer
Workstation
object
14 properties 2 required
TeamApiCode
object
4 properties 1 required
EventAttributes
integer
PropertyInfo
object
15 properties
Person
object
27 properties 3 required
ServiceNowPropertyWrapper
object
1 property
MethodBase
object
32 properties
RuntimeMethodHandle
object
1 property
Role
object
3 properties 1 required
CustomAttributeTypedArgument
object
2 properties
WorkstationAssignment
object
13 properties
ParameterInfo
object
15 properties
ServiceNowProperties
object
25 properties
TypeAttributes
integer
ConstructorInfo
object
32 properties
Type
object
71 properties
Team
object
13 properties 2 required
IntPtr
object
ModuleHandle
object
1 property
MemberInfo
object
8 properties
EquipmentAttributeKey
object
5 properties 2 required
Group
object
4 properties 1 required
RuntimeTypeHandle
object
1 property
Space
object
18 properties
FinancialOrganization
object
6 properties 3 required
GroupPermission
object
5 properties 2 required
MemberTypes
integer
CallingConventions
integer
Access
object
9 properties 1 required
RuntimeFieldHandle
object
1 property
Assembly
object
18 properties
EventInfo
object
15 properties
LayoutKind
integer
KeyXSpace
object
5 properties 2 required
TeamPermission
object
7 properties 3 required
GenericParameterAttributes
integer
CustomAttributeNamedArgument
object
4 properties
ICustomAttributeProvider
object
StructLayoutAttribute
object
2 properties
Module
object
9 properties
PropertyAttributes
integer
FieldInfo
object
26 properties
KeySerialAssignment
object
14 properties
Filter
integer

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

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

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) — Keys API
PEAKS (CAES) — KeySerials API
PEAKS (CAES) — People API
PEAKS (CAES) — PeopleAdmin API
PEAKS (CAES) — Spaces API
Where this information came from

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