Topic Guides

Topic Guides

Related articles grouped by topic.

Industry Search Hubs

Short, search-friendly entry pages for travel technology teams evaluating hotel API integration and HotelByte OpenAPI.

• Hotel API Integration Guide for Travel Companies

  Supplier direct connection, hotel API aggregation, room mapping, price normalization, rate limits, and booking-flow reliability.

• HotelByte OpenAPI Hotel Distribution Guide

  Authentication, Customer Certification, booking flow, Error Handling, content APIs, and health checks from the docs/api source set.

Hotel API Integration Field Notes

Real integration lessons across authentication, data normalization, rate limits, error handling, timezones, and room mapping.

• Part 1 Why Hotel API Integration Is So Hard (1): Authentication Hell - 10 Weeks Planned, 24 Weeks Still Not Done

  5 suppliers, 5 different authentication methods—Basic Auth, HMAC-SHA256, OAuth1, JWT...

• Part 2 Why Hotel API Integration Is So Hard (2): Data Chaos - Same Hotel, 5 Different Data Formats

  The same hotel can arrive with different schemas, field meanings, and room structures from each supplier.

• Part 3 Why Hotel API Integration Is So Hard (3): Rate Limiting Nightmare - Blocked 3 Times on Day 1

  Supplier rate limits, hotspot detection, and blocking behavior can break search on launch day.

• Part 4 Why Hotel API Integration Is So Hard (4): Error Handling - Same Error, 5 Different Status Codes

  Supplier error codes are inconsistent, and HTTP status codes are often misused...

• Part 5 Why Hotel API Integration Is So Hard (5): Timezone Issues - User Booked Yesterday's Hotel

  UTC, hotel-local time, user-local time, and daylight saving rules can shift stay dates.

• Part 6 Why Hotel API Integration Is So Hard (6): Room Mapping - Same Room, 5 Different Names

  The same physical room can have different names, photos, and attributes across suppliers.

• Part 7 Why Hotel API Integration Is So Hard (Final): Why Can We Solve These Problems?

  Reviewing entire API integration process and summarizing best practices...

AI Coding Practice

From DeepSeek to Claude Code, exploring practice and experience of AI-assisted programming.

• AI Coding Practice: Journey from DeepSeek to Claude Code

  We experimented with various AI coding tools in HotelByte project...

• AI Coding Practice (1): Migration from DeepSeek to Claude Code

  How to switch from DeepSeek to Claude Code while maintaining code quality...

• AI Coding Practice (2): Deep Claude Code Integration

  Integrating Claude Code into our development workflow...

• AI Coding Practice (3): Multi-Model and Toolchain Integration

  Using multiple AI models simultaneously to leverage their strengths...

• AI Coding Practice (4): OpenSpec-Driven Development

  Using OpenSpec specifications to drive AI-assisted development...

• AI Coding Practice (5): AI Coding Best Practices

  Summarizing best practices and considerations for AI coding...

HTTP Dispatcher

Deep dive into design and implementation of HTTP Dispatcher.

• HTTP Dispatcher (1): What Is HTTP Dispatcher and Why It's Needed for Hotel API Integration

  Introducing concept and role of HTTP Dispatcher...

• HTTP Dispatcher (2): How HTTP Dispatcher Solves Rate Limiting and Connection Pooling

  How to implement efficient rate limiting and connection pool management...

• HTTP Dispatcher (3): Implementing HTTP Dispatcher in Go

  Implementing HTTP Dispatcher using Go language...

Supplier Proxy

Design and implementation of supplier proxy.

• Supplier Proxy (1): What Is Supplier Proxy and Its Role in Hotel API Aggregation

  Introducing concept and role of Supplier Proxy...

• Supplier Proxy (2): How Supplier Proxy Handles Authentication and Error Handling

  How to handle authentication and errors in Supplier Proxy...