HTTP
REST API
On-demand access for query-based feeds.
- Cadence
- Request-time
Protected API access
Limited anonymous access / verification required
Reliable data, ready to integrate.
Query airline, hotel, shipment, and marketplace data from published sources.
Coverage is confirmed, not implied. The query console above demonstrates protected requests and normalized response formats; sources and markets are checked before integration.
Data catalog
Feed types available for scoping
Exact fields, sources, regional coverage, and cadence are confirmed against each request.
| Feed ID | Feed | Data returned | Update | Delivery | Coverage |
|---|---|---|---|---|---|
| TRV-FLIGHT-01 | TravelFlight search | Itineraries, schedules, fares, and availability | Per query or agreed cadence | API or feed, as scoped | Airlines, routes, and points of sale confirmed per request |
| TRV-HOTEL-01 | TravelHotel rates | Properties, room types, rates, and availability | Per query or agreed cadence | API or feed, as scoped | Properties and markets confirmed per request |
| COM-SEARCH-01 | E-commerceProduct search | Product IDs, titles, prices, sellers, and result ranking | Per query | API, as scoped | Platform, region, and category confirmed per request |
| COM-DETAIL-01 | E-commerceProduct detail | Attributes, variants, offers, seller, inventory, and media | Per query | API, as scoped | Platform, product type, and region confirmed per request |
| LOG-TRACK-01 | LogisticsShipment tracking | Carrier, current status, scan events, and exceptions | Source-dependent cadence | API or event feed, as scoped | Carriers and lanes confirmed per request |
Fields are subject to source availability. Coverage and cadence are not universal; both are documented in the feed specification.
Coverage
Coverage is assessed against the actual requirement.
A platform or carrier name does not imply complete coverage across every region, category, route, or record type. We check the requested scope before an integration starts.
Request a coverage check →Coverage check / required inputs
- Target sources
- Platforms, carriers, airlines, or properties
- Markets
- Regions, routes, points of sale, or categories
- Records and fields
- The exact values your product needs
- Update cadence
- Query-time, monitored, or scheduled delivery
- Expected volume
- Requests, records, or tracked objects
- Known limitations
- Documented with the proposed feed
Delivery
Delivery methods
The delivery method is selected per feed and confirmed before implementation.
FILE
Scheduled files
Recurring snapshots in an agreed format and cadence.
- Cadence
- Agreed schedule
EVENT
Webhooks or event feeds
Status changes and new events, where supported by the source and feed.
- Cadence
- Source-dependent
Quality
Quality terms are written into the feed specification.
We define what will be measured before production. SLAs are stated only when contractually agreed.
- Source coverage
- Which sources, markets, and record types are included.
- Freshness target
- When a value is observed and the expected delivery window.
- Required-field completeness
- Which fields are required, optional, or source-dependent.
- Error behavior
- How partial data, source errors, and unavailable records are represented.
- Delivery monitoring
- How feed failures and delayed deliveries are identified.
- Incident contact
- The escalation path agreed for the engagement.
Request coverage
Send the source, market, fields, volume, and cadence.
We will confirm what can be supplied, known source limitations, and the delivery methods available for the feed.
Request a coverage check hello@geniuspacket.com