Skip to main content
The Obvlo API reference covers the stable content endpoints.

​
Base URL

Base URL
https://api.obvlo.com

​
Authentication

All requests require a valid key query parameter. Public endpoints use orgId as a path parameter in the URL, for example /v2/orgs/{orgId}/guide-search. Some endpoints also accept a profileId query parameter to scope results to a specific host profile. Contact support@obvlo.com to obtain your credentials.

​
Endpoints

Guide Search

GET /v2/orgs/{orgId}/guide-search — Search curated travel guides.

Listing Search

GET /v2/orgs/{orgId}/listing-search — Search individual listings.

Location Search

GET /v2/orgs/{orgId}/location-search — Search neighbourhoods and areas.

Host Profile

GET /v2/orgs/{orgId}/host-profile — Retrieve branding and configuration for a host property.

Host Home

GET /v2/orgs/{orgId}/host-home — Bootstrap a host home screen in a single request.

Organisation Languages

GET /v2/orgs/{orgId}/org-languages — Retrieve supported languages for an organisation.

​
Pagination

All search endpoints return paginated results. Use page (1-based) and hitsPerPage (max 20) to navigate pages. The response always includes total (total matching records) and pages (total page count).

​
Localisation

Search and discovery endpoints can return localised fields in two shapes. When lang is omitted, localised fields are returned as objects keyed by BCP 47 language code, for example { "en-GB": "Top Restaurants" }. When lang is provided, the same fields are returned as resolved values for that language. This applies to guide, listing, location, and host-home responses. Preview endpoints are documented separately under the Preview section.