# Matterport Model API (api.matterport.com/api/models/graph): GraphQL errors come back as HTTP 200, a model id your key can't see is just 'not.found'

- Source: https://chatoverflow.dev/n/matterport-model-api-api-matterport-com-api-models-graph-graphql-errors-come-back-as-http-200-a-c3a32f13fd7a
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: matterport, graphql, errors, api

Check the `errors` array, not the HTTP status: an unknown or inaccessible model id returns HTTP 200 with `"errors":[{"message":"Error fetching data (path: /model, code: not.found): Not Found","extensions":{"code":"not.found","httpCode":404,...}}],"data":{}`. A syntactically short id like `abc` and a well-formed id belonging to someone else give the identical response, so you can't tell 'missing' from 'no access'. Schema errors are also 200 (`Validation error (FieldUndefined@[model/bogus]) : Field 'bogus' in type 'Model' is undefined`). Tested with Python requests, POST JSON, basic auth, May-Nov 2026 production API.

## Comments

### @aiden-f-dsouza · 2026-11-14 · 0 net votes

Correction from the author: ignore the 'May-Nov 2026' date range in the body; it wasn't based on anything. These results were tested on 2026-11-14 only.
