---
title: "Stuba: B2B Hotel Distribution API Profile"
description: "A technical profile of Stuba's hotel distribution APIs covering content, live availability, quote refresh, booking and cancellation workflows."
slug: "stuba"
translationKey: "platform-stuba"
locale: "en"
type: "profile"
category: "travel-ecosystem"
tags: ["stuba","hotel-api","bedbank","b2b","hotel-distribution"]
platform: "Stuba"
domain: "stuba.com"
vertical: ["hotel"]
publishedAt: "2026-09-27"
updatedAt: "2026-09-27"
reviewedAt: "2026-09-27"
technicalVerifiedAt: "2026-09-27"
directory: {"status":"active","reviewedAt":"2026-09-27","platformType":"bedbank","roles":["bedbank","b2b-marketplace","api"],"ecosystemLayers":["connectivity-distribution","booking-transaction"],"turkeyRelevance":"global-context","audiences":["b2b"],"businessModels":[],"integrationMethods":["api"],"docsUrl":"https://developer.stuba.com/","directSupplierParticipation":"no","developerDocsAvailable":"yes","sources":[{"title":"Stuba Developer Portal","url":"https://developer.stuba.com/"},{"title":"Stuba API Getting Started","url":"https://developer.stuba.com/hapi/getting-started/"}]}
sources:
  - title: "Stuba Developer Portal"
    url: "https://developer.stuba.com/"
  - title: "Stuba API Getting Started"
    url: "https://developer.stuba.com/hapi/getting-started/"
---
Stuba exposes a public B2B hotel-distribution developer portal with content and booking APIs, test access, certification and production onboarding.

## Core lifecycle

```text
Hotel/Region Search
 -> result / quote identity
 -> BookingPrepare (refresh)
 -> BookingConfirm
 -> BookingQuery / HCN
 -> BookingCancel
```

This makes Stuba a strong canonical example of search → recheck → booking semantics.

## Access model

The current JSON API uses an AuthApiKey and IP allowlisting. Stuba documents separate test and production environments and requires certification before live access.

## Content vs live search

Content API and live availability should have different freshness models. Property/content mapping should not depend on ephemeral search result IDs.

## Performance note

Stuba publicly notes availability response times can vary by search shape. Multi-supplier metasearch should therefore use provider-specific latency budgets rather than blocking on Stuba indefinitely.

## Failure modes

- stale quote/result identity,
- skipped BookingPrepare,
- IP/auth mismatch,
- booking UNKNOWN state,
- hotel/room mapping drift.

## Observability

Track search latency, quote-refresh changes, booking-confirm unknown state, cancellation status and content/live mapping coverage.