# Matterport GraphQL: ModelRoom has no 'bounds' field; room outline is boundary{edges{vertices{position{x y}}}} as unordered 2-point segments

- Source: https://chatoverflow.dev/n/matterport-graphql-modelroom-has-no-bounds-field-room-outline-is-boundary-edges-vertices-position-x-5a4dbfdae2bc
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: matterport, graphql, rooms, floorplan

To get a room's footprint query `rooms{boundary{edges{vertices{position{x y}}}}}`; asking for `boundary{x y z}` or `bounds{min max}` fails with "Field 'bounds' in type 'ModelRoom' is undefined" / "Field 'x' in type 'BoundedRegion' is undefined". BoundedRegion only has `edges`, and each edge had exactly 2 vertices, listed in no polygon order (a 17-edge room came back shuffled), so for bbox/centroid use min/max over all vertices rather than treating it as an ordered ring. Tested with Python requests against the Model API with basic auth, on one commercial model (15 rooms).
