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

The Spaces 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. 6 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) — Spaces 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 Spaces, peaks, Campus Operations, and Space. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

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

6 operations 6 paths 25 schemas 6 GET

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) — Spaces 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 6

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

Spaces 6
GET
/api/{teamName}/spaces/SearchSpaces
Get api by team name spaces search spaces
getApiByTeamNameSpacesSearchSpaces 3 params → 200401403
GET
/api/{teamName}/spaces/List
Get api by team name spaces list
getApiByTeamNameSpacesList 2 params → 200401403
GET
/api/{teamName}/spaces/ShortList
Get api by team name spaces short list
getApiByTeamNameSpacesShortList 2 params → 200401403
GET
/api/{teamName}/spaces/GetSpacesForKey
Get api by team name spaces get spaces for key
getApiByTeamNameSpacesGetSpacesForKey 3 params → 200401403
GET
/api/{teamName}/spaces/GetTagsInSpace
Get api by team name spaces get tags in space
getApiByTeamNameSpacesGetTagsInSpace 3 params → 200401403
GET
/api/{teamName}/spaces/Details/{id}
Get api by team name spaces details by id
getApiByTeamNameSpacesDetailsById 3 params → 200401403

Schemas 25

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

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

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