Hipcamp API

Does Hipcamp have a public API?

No. Hipcamp publishes no public developer API. Hosts running a supported property management system or channel manager can ask Hipcamp by email to connect it, and that integration syncs the host's own calendar, pricing and bookings. Nothing is offered on the camper side, and there is no developer portal or self-serve key. Integuru's Hipcamp integration provides 21 verified actions over direct HTTP requests, authenticated with your own Hipcamp camper account.

| | Hipcamp host integrations | Integuru for Hipcamp | |---|---|---| | Access | Arranged by email for hosts on a supported PMS | Your own camper login | | Covers | The host's own calendar, pricing and bookings | Search, availability, reviews, alerts, saved lists, trips and messages | | Best for | Campground operators | Trip planners, agents and apps acting for a camper |

What you can do with the Hipcamp API

The verified actions follow a camper planning a long weekend: search, inspect a listing, check the dates, set an alert if the dates are gone, and keep the shortlist somewhere.

Search and inspect. search_campsites takes a free-text location (geocoded for you) or a latitude and longitude pair, optional arrive and depart dates, and a party of adults (default 2), children and pets. limit defaults to 20 and caps at 50; offset pages. get_listing_details takes a land_id, which accepts the 8-character masked id from a listing URL, the full URL, or the numeric primary key when land_id_type is PRIMARY_KEY. get_listing_photos pages with after and can drop camper photos with host_photos_only. get_listing_reviews filters by camping_style and orders with sort_by; get_site_reviews narrows to one site_id. get_camper_profile takes the slug of any review author and returns that camper's public profile with paged reviews_written and feedback_received.

Check the dates. get_listing_availability takes land_id, arrive, depart and the party size and returns every site on the listing, marking which match. It pages through the listing internally, so count and available_count describe the whole listing; max_sites (default 500, cap 2000) only bounds very large campgrounds and sets has_more when it bites. Each site node carries a campgroundId. get_listing_reserved_days returns the reserved calendar for a listing or one campsite_id, filtered locally by start_date and end_date.

Watch for a cancellation. create_availability_alert takes the campground_id from the availability response (not the listing id) and a start_date and end_date range. list_availability_alerts pages with after and filters by statuses; cancel_availability_alert takes an alert_id.

Keep a shortlist. create_saved_list takes a name, rename_saved_list and delete_saved_list take a saved_list_id, and the account's default Wishlist cannot be deleted. list_saved_listings returns the lists with up to items_per_list items inline (default 50, cap 100).

Your account. get_my_profile, list_my_trips (status defaults to UPCOMING, limit caps at 50), list_message_threads (limit default 15, filters, participant_first_name), get_my_reviews, get_trip_story (takes the review_uuid from get_my_reviews or get_camper_profile, not the contributed_tip_uuid from listing reviews) and get_my_patches with user_type CAMPER or HOST.

The booking step is built on request through the Managed Service.

Who uses this

Trip-planning assistants take a place and two dates, call search_campsites, run get_listing_availability on the top results and answer with sites that are actually open, in the tool-calling loop described on the AI agents page. The same agents pair a found site with a hike from AllTrails. Cancellation-alert products give a camper one place to manage create_availability_alert across several campgrounds. Travel apps that let a user connect Hipcamp import list_my_trips and list_saved_listings so past stays and the wishlist come with the user.

Setup notes

Integuru authenticates against www.hipcamp.com with the camper's own credentials and returns that account's trips, lists, alerts and messages plus the listing data any signed-in camper can view. Dates are YYYY-MM-DD and depart must fall strictly after arrive. Cursors are opaque: the listing actions and alerts use after, trips, messages and saved lists use cursor, and in every case you pass back the next_cursor from the previous response. Keep the campgroundId from an availability response if you plan to set an alert.

Get started

Install the CLI and connect your Hipcamp login:

npm install -g integuru

Or sign in at app.integuru.com and add Hipcamp. To add the booking step, the Managed Service scopes and builds it against your account. The integrations catalogue lists every live platform.