Omnibees Hotel API Integration via Vervotech

Integration snapshot

Supplier

Omnibees

Type

Distribution

Origin country

Brazil

Region

Americas

Coverage tier

Production-grade

Canonical mapping

Vervotech hotel + room IDs

Schema unification

Names, addresses, geocodes, amenities, room types, board types

Delivery

REST API, offline file sync, on-demand match

What Vervotech does for Omnibees

• Canonical hotel IDs. Each Omnibees property resolves to a single Vervotech hotel ID shared with every other connected supplier.
• Room-level mapping. Identical room types from Omnibees collapse with peer suppliers' equivalents into a canonical room ID, so you can shop rates without duplicate inventory.
• Continuous refresh. Static and dynamic Omnibees content is pulled on a recurring cycle, so newly contracted properties enter the mapped catalog without engineering work.
• One REST endpoint. Call Omnibees content through the same Vervotech endpoint that serves the rest of your supplier mix.

How the Omnibees integration works

1. Ingest. Vervotech pulls the Omnibees hotel content feed on a continuous refresh cycle. Both static (hotel attributes) and structural (room and board types) data are captured.
2. Normalize. Omnibees's schema is mapped to a canonical Vervotech model. Currency, language, geocoding, and amenity vocabularies are standardized.
3. Resolve. Every Omnibees property is matched to a canonical Vervotech hotel ID using deterministic rules (address, geocode, name) and ML scoring trained on 3M+ properties.
4. Deduplicate rooms. Equivalent room types from Omnibees are collapsed with peer supplier rooms into a canonical room ID.
5. Expose. Omnibees content is reachable through one Vervotech REST endpoint, mixed with the rest of your supplier inventory.

Example Omnibees response via Vervotech

Vervotech returns Omnibees properties enriched with canonical IDs that match the same property as served by peer suppliers.

GET /v3/hotels?supplier=omnibees&country=br
Authorization: Bearer YOUR_VERVOTECH_KEY

200 OK
{
  "supplier": "Omnibees",
  "hotels": [
    {
      "vervotech_id": "vt_8f3a91...",
      "omnibees_id": "SUP_REF_12345",
      "name": "Example Hotel Omn",
      "address": "...",
      "geo": { "lat": ..., "lng": ... },
      "rooms": [ { "vervotech_room_id": "vrm_...", "omnibees_room_id": "RM_77" } ]
    }
  ]
}

Schema is illustrative. See the Hotel Mapping API documentation for the full spec.

Vervotech-mapped Omnibees vs direct Omnibees integration

Typical Omnibees use cases

• OTAs and metasearch: blend Omnibees rates with peer suppliers behind a single property listing, with no duplicates and no schema drift.
• Travel agencies and TMCs: route bookings to Omnibees when its rate wins, fall back to alternates when it does not, all under one mapped catalog.
• Corporate travel: normalize Omnibees content into one travel-policy view across regions and brands.
• Post-booking margin capture: watch Omnibees and peer rates after the original booking and rebook automatically via Vervotech Profit Maximizer when a cheaper rate appears.

Related Vervotech capabilities

• Hotel Mapping API99.998% accuracy at 3M+ properties
• Room Mapping APICanonical room IDs across suppliers
• Profit MaximizerPost-booking margin capture across Omnibees and peers
• All 153+ suppliersBrowse the full supplier network