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

Smoobu Reservations API

Bookings across all connected channels and their price elements.

Smoobu Reservations API is one of 6 APIs that Smoobu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://login.smoobu.com.

7 operations 3 paths 1 schemas 1 DELETE3 GET2 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://login.smoobu.com/api
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Smoobu Reservations API declares 1 security scheme for authenticating requests. An API key is passed in the header as Api-Key (apiKey). By default, every request must be authenticated.

  • apiKey — Smoobu API key sent in the Api-Key header. HMAC-signed requests (X-API-Key / X-Timestamp / X-Nonce / X-Signature) are the recommended method; OAuth 2 is availa…

Paths & Operations 7

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

Reservations 7

Bookings across all connected channels and their price elements.

GET
/api/reservations
List reservations
listReservations 17 params → 200401
POST
/api/reservations
Create a reservation
createReservation body → 200401422
GET
/api/reservations/{reservationId}
Get a reservation
getReservation 1 param → 200401404
PUT
/api/reservations/{reservationId}
Update a reservation
updateReservation 1 param body → 200401404
DELETE
/api/reservations/{reservationId}
Delete a reservation
deleteReservation 1 param → 200401404
GET
/api/reservations/{reservationId}/price-elements
List price elements
listPriceElements 1 param → 200401
POST
/api/reservations/{reservationId}/price-elements
Create a price element
createPriceElement 1 param body → 200401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ReservationInput (12 properties). Each schema is shown below with its type and property counts.

ReservationInput
object
12 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smoobu-reservations-api-openapi.yml Raw ↑

Other APIs Smoobu publishes across the network.

Smoobu Apartments API
Smoobu Guests API
Smoobu Messaging API
Smoobu Rates and Availability API
Smoobu User API
Where this information came from

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