Skip to main content
Solved

include=property not returned in /reservations response (v2 API)


Hi everyone 👋,

I’m integrating the Public API v2 with Zapier + ChatGPT and have hit a road-block when trying to embed property data in a reservation response. I’d love a sanity-check from the community (or the API team) to see if I’m missing something or if this is a bug.

1 Request I’m sending

 

http

复制

GET /v2/reservations/8bc5e1b9-1b78-4903-8ce9-c92f3a7faadc?include=property Host: public.api.hospitable.com Authorization: Bearer <personal‐access‐token>

Token scopes

  • reservations:read

  • properties:read

(Confirmed in Settings → API 访问.)

2 Expected

Per the docs (“Show Reservation” endpoint) the response should contain

 

json

复制

"relationships": { "property": { ... } }, "included": [ { "type": "property", "attributes": { "name": "Loft A302", ... } } ]

3 Actual (200 OK, truncated)

 

json

复制

{ "data": { "id": "8bc5e1b9-1b78-4903-8ce9-c92f3a7faadc", "code": "HMXZTQ5E3Z", "platform": "airbnb", "arrival_date": "2025-06-15", "departure_date": "2025-06-19", "status": "accepted", "conversation_id": "d5f58806-7c17-4d42-8092-5afada8cae75" } }

No relationships.property and no included array at all.

4 What I’ve already checked

Test Result
Same request without include=property Identical response (so the query string is recognised but ignored).
/v2/reservations/{id}?include=guest Guest object does appear in included
/v2/properties/{property_id} with the same token Returns full property JSON ✅
Tried two other reservation IDs (Airbnb, status = accepted) Same outcome ❌
Tools Hoppscotch, Postman, Zapier Custom Request – all identical.

 

5 Questions

  1. Is include=property currently supported for Airbnb reservations?

  2. Are there additional filters (e.g. fields[properties]) or relationship flags we need to set?

  3. Could this be a recent regression? (Changelog 2025-05-xx mentions webhook updates.)

Happy to provide full response headers or Postman collection exports if that helps reproduce.

Thanks in advance for any insights! 🙏

 

— [wang yan]
 Chiang Mai, TH

Best answer by Mahmodul

It’s include=properties

not property.

 

const url = 'https://public.api.hospitable.com/v2/reservations/drsdsrgsfdg-83d0-1eb8f494783a?include=properties';
const options = {
  method: 'GET',
  headers: {
    'Content-Type': '',
    Accept: 'application/json',
    Authorization: 'Bearer .ghgdfghsf'
  }
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

Hope it helped. 

View original
Did this topic help you find an answer to your question?

3 replies

Mahmodul
Top Contributor
Forum|alt.badge.img+1
  • Top Contributor
  • 68 replies
  • Answer
  • June 14, 2025

It’s include=properties

not property.

 

const url = 'https://public.api.hospitable.com/v2/reservations/drsdsrgsfdg-83d0-1eb8f494783a?include=properties';
const options = {
  method: 'GET',
  headers: {
    'Content-Type': '',
    Accept: 'application/json',
    Authorization: 'Bearer .ghgdfghsf'
  }
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

Hope it helped. 


Mahmodul
Top Contributor
Forum|alt.badge.img+1
  • Top Contributor
  • 68 replies
  • June 14, 2025

Also, my question to the dev team: why "properties"? Shouldn’t it be "property" 🙄? Isn’t it a one-to-one relationship? Is it just to make the format consistent?
 


Luke Renfrew
Hospitable Team Member
Forum|alt.badge.img
  • Hospitable Team Member
  • 4 replies
  • June 15, 2025

@Mahmodul Great question. I think was just to align it with listings. As a reservation can actually be associated to multiple listings ( in  the case of Booking.com multi-listing reservation )

But you are right and all those listings would be the same property so we are only ever going to return one property! 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings