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

Luxury Presence Offices API

The Offices API from Luxury Presence — 5 operation(s) for offices.

Luxury Presence Offices API is one of 5 APIs that Luxury Presence publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Offices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

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

Requests are made against a single base URL, https://api.luxurypresence.com.

10 operations 5 paths 11 schemas 3 DELETE3 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.luxurypresence.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Luxury Presence Offices API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — API key generated from the Luxury Presence dashboard (Settings API Keys). Sent as the x-api-key request header.

Paths & Operations 10

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

Offices 10
GET
/cms/v1/offices
Fetch existing offices
OfficesController_handleGetOffices 5 params → 200
POST
/cms/v1/offices
Create a new office
OfficesController_handlePostOffice body → 201
GET
/cms/v1/offices/{id}
Fetch an existing office
OfficesController_handleGetOffice 1 param → 200404
PATCH
/cms/v1/offices/{id}
Update an existing office
OfficesController_handlePatchOffice 1 param body → 200404
DELETE
/cms/v1/offices/{id}
Delete an office
OfficesController_handleDeleteOffice 1 param → 200404
POST
/cms/v1/offices/bulkCreate
Bulk create new offices
OfficesController_handleBulkCreateOffices body → 201400
DELETE
/cms/v1/offices/bulkDelete
Delete multiple offices
OfficesController_handleBulkDeleteOffice 1 param → 200404
GET
/cms/v1/offices/{id}/agents
Fetch members of a specific office
OfficesController_handleGetOfficeAgents 3 params → 200
DELETE
/cms/v1/offices/{id}/agents
Remove members from a specific office
OfficesController_handleDeleteOfficeAgents 1 param body → 200
POST
/cms/v1/offices/{id}/agents
Add agent(s) to an office
OfficesController_handlePostOfficeAgents 1 param body → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are CreateOfficeDto (17 properties), OfficeDto (15 properties), UpdateOfficeDto (15 properties), AddressDto (6 properties). Each schema is shown below with its type and property counts.

OfficeHoursDto
object
5 properties
GetOfficesResponseDto
object
2 properties 2 required
BulkCreateOfficeDto
object
1 property 1 required
UpdateOfficeDto
object
15 properties
DeleteOfficeAgentDto
object
1 property 1 required
CreateOfficeAgentDto
object
1 property 1 required
CreateOfficeDto
object
17 properties 1 required
OfficeDto
object
15 properties 1 required
AddressDto
object
6 properties
WorkingHoursDto
object
3 properties
CoordinatesDto
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

luxury-presence-offices-api-openapi.yml Raw ↑

Other APIs Luxury Presence publishes across the network.

Luxury Presence Agents API
Luxury Presence Media API
Luxury Presence Teams API
Luxury Presence Webhooks API
Where this information came from

This is an independent, third-party profile of Luxury Presence Offices 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.