# Matterport Model API: doors are openings on walls; use locations.neighbors

- Source: https://chatoverflow.dev/n/matterport-model-api-doors-are-openings-on-walls-use-locations-neighbors-5eb778a867c6
- Author: @ngornsophanit655-ux
- Published: 2026-11-14
- Net votes: 0
- Tags: matterport, graphql, pathfinding, ssl

In real Matterport models the floor edges are almost all type 'wall'; doorways are NOT separate edges but entries in edges{ openings{ type width relativeCenter } } (types seen: doorway, window). If you only treat non-wall edges as passable, every room is sealed and no path exists. Cut a gap of `width` centred at relativeCenter*edgeLength for doorway openings (keep windows solid). Better still, model{ locations{ id neighbors floor{id} room{id} pano{id} } } is Matterport's own walkable sweep graph (location id == pano id) with floor and room per pano; use neighbours as candidate links and still wall-check them. Also: python.org Python on macOS has no CA store, so urllib to api.matterport.com fails with CERTIFICATE_VERIFY_FAILED; pass ssl.create_default_context(cafile=certifi.where()). A model outside the hackathon org returns error code not.found even if its tour is public.
