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

Kadence Visit API

The Visit API from Kadence — 2 operation(s) for visit.

Kadence Visit API is one of 11 APIs that Kadence publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Visit. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

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

Requests are made against 2 base URLs: https://api.onkadence.co, https://api.us.onkadence.co.

2 operations 2 paths 6 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.0
Base URL
https://api.onkadence.co
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Kadence Visit API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • oauth — OAuth 2.0 client credentials Grant

Paths & Operations 2

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

Visit 2
GET
/v1/public/visits
Get visits
api_v1publicvisits_get_collection 20 params → 200
GET
/v1/public/visits/{id}
Get a single visit by identifier
api_v1publicvisits_id_get 2 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Visit.jsonld-public_visit (10 properties), Visit-public_visit (7 properties), User.jsonld-public_visit (3 properties), Ulid.jsonld-public_visit (3 properties). Each schema is shown below with its type and property counts.

User-public_visit
object
Ulid-public_visit
object
Ulid.jsonld-public_visit
object
3 properties
Visit-public_visit
object
Read-only public representation of a visit. A visit is a guest {@see Booking} viewed through the visits lens. It surfaces the host, building, time window and s…
7 properties
Visit.jsonld-public_visit
object
Read-only public representation of a visit. A visit is a guest {@see Booking} viewed through the visits lens. It surfaces the host, building, time window and s…
10 properties
User.jsonld-public_visit
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kadence-visit-api-openapi.yml Raw ↑

Other APIs Kadence publishes across the network.

Kadence Bookable Day API
Kadence Bookable Onsite Pass API
Kadence Bookable Space API
Kadence Booking API
Kadence Building API
Kadence Floor API
Kadence Neighborhood API
Kadence Space API
Kadence User API
Kadence Visitor API
Where this information came from

This is an independent, third-party profile of Kadence Visit 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.