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 18 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.0.1, 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.0.1
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
3 params → 200401403
GET
/api/{teamName}/equipment/SearchAttributes
3 params → 200401403
GET
/api/{teamName}/equipment/GetEquipmentInSpace
3 params → 200401403
GET
/api/{teamName}/equipment/CommonAttributeKeys
2 params → 200401403
GET
/api/{teamName}/equipment/ListEquipmentTypes
2 params → 200401403
GET
/api/{teamName}/equipment/ListAssigned
3 params → 200401403
GET
/api/{teamName}/equipment/List
List all equipments for a team
3 params → 200401403
GET
/api/{teamName}/equipment/Details/{id}
4 params → 200401403
POST
/api/{teamName}/equipment/Create
2 params body → 200401403
POST
/api/{teamName}/equipment/Duplicate
2 params body → 200401403
POST
/api/{teamName}/equipment/Assign
5 params → 200401403
POST
/api/{teamName}/equipment/Update
2 params body → 200401403
POST
/api/{teamName}/equipment/Revoke/{id}
3 params → 200401403
POST
/api/{teamName}/equipment/Delete/{id}
3 params → 200401403
GET
/api/{teamName}/equipment/GetHistory/{id}
Takes the top 5 history records
4 params → 200401403
GET
/api/{teamName}/equipment/GetComputer/{id}
3 params → 200401403
GET
/api/{teamName}/equipment/GetComputersBySearch
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), MethodBase (32 properties). Each schema is shown below with its type and property counts.

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

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.

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) — Keys API
PEAKS (CAES) — KeySerials API
PEAKS (CAES) — People 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.