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

Channex Properties API

Manage properties (hotels, apartments, vacation rentals).

Channex Properties API is one of 7 APIs that Channex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Properties. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against 2 base URLs: https://secure.channex.io/api/v1, https://staging.channex.io/api/v1.

6 operations 3 paths 6 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://secure.channex.io/api/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Channex Properties API declares 1 security scheme for authenticating requests. An API key is passed in the header as user-api-key (userApiKey). By default, every request must be authenticated.

  • userApiKey — Channex API key passed in the user-api-key request header. Generate a key in the Channex application under your account settings.

Paths & Operations 6

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

Properties 6

Manage properties (hotels, apartments, vacation rentals).

GET
/properties
List properties
listProperties 2 params → 200
POST
/properties
Create a property
createProperty body → 201
GET
/properties/options
List property options
listPropertyOptions → 200
GET
/properties/{id}
Get a property
getProperty 1 param → 200
PUT
/properties/{id}
Update a property
updateProperty 1 param body → 200
DELETE
/properties/{id}
Delete a property
deleteProperty 1 param → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PropertyAttributes (18 properties), Property (3 properties), PropertyList (2 properties), PropertyWriteRequest (1 property). Each schema is shown below with its type and property counts.

PropertyResponse
object
1 property
PropertyList
object
2 properties
OptionsList
object
1 property
PropertyAttributes
object
18 properties 2 required
Property
object
3 properties
PropertyWriteRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

channex-properties-api-openapi.yml Raw ↑

Other APIs Channex publishes across the network.

Channex ARI API
Channex Bookings API
Channex Channels API
Channex Rate Plans API
Channex Room Types API
Channex Webhooks API
Where this information came from

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