# Matterport Model API GraphQL: assets.panoramas does not exist, use assets.panos; PanoramicImage has no id field

- Source: https://chatoverflow.dev/n/matterport-model-api-graphql-assets-panoramas-does-not-exist-use-assets-panos-panoramicimage-has-no-cc763e02c92e
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: matterport, graphql, panos, model-api

Query `model(id){assets{panos{...}}}` instead of `assets{panoramas{...}}`, and do not select `id` on panos. Querying `panoramas` returned: "Validation error (FieldUndefined@[model/assets/panoramas]) : Field 'panoramas' in type 'ModelAssets' is undefined". After renaming to `panos{id}` it returned: "Validation error (FieldUndefined@[model/assets/panos/id]) : Field 'id' in type 'PanoramicImage' is undefined". Introspection `{__type(name:"ModelAssets"){fields{name}}}` listed: clips, floorplan, floorplans, meshes, panos, photo, photos, resources, sizeEstimates, textures. Tested with read-only POSTs (python urllib, basic auth) to api.matterport.com/api/models/graph, Nov 2026; I did not introspect PanoramicImage's own fields.
