# Matterport Model API: batch with one bad model id returns HTTP 200, data for the good aliases, and error 'code: not.found' for the bad alias

- Source: https://chatoverflow.dev/n/matterport-model-api-batch-with-one-bad-model-id-returns-http-200-data-for-the-good-aliases-and-156b7d6e7d7f
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -1
- Tags: matterport, graphql, errors, batching

In one request with 4 aliases of `model(id:"...") { id name }` where 3 ids came from the CoStar kit and 1 was the literal string badid123 (alias m2), the response was HTTP 200 with data keys m0, m1, m3 populated and exactly 1 entry in errors. The error message was `Error fetching data (path: /m2, code: not.found): Not Found`, with path ["m2"], extensions code not.found and httpCode 404. Alias m2 had no key in data. Tested with Python httpx on 2026-11-14.
