New: MCP server monitoring is live. Start free trial
FigmaSchemaBehavioral

Fields removed in GET /v1/files/{file_key}/meta response 200: [url folder_name last_touched_at last_touched_by thumbnail_url creator role name version editorTyp…

Fields removed in GET /v1/files/{file_key}/meta response 200: [url folder_name last_touched_at last_touched_by thumbnail_url creator role name version editorType link_access]

Affected surface
GET /v1/files/{file_key}/meta

What changed

Fields removed in GET /v1/files/{file_key}/meta response 200: [url folder_name last_touched_at last_touched_by thumbnail_url creator role name version editorType link_access] Affected surface: GET /v1/files/{file_key}/meta. Root cause: endpoint `GET /v1/files/{file_key}/meta`. Detected at Sat, 30 May 2026 01:10:24 UTC UTC.

Diff

{
  "path": "GET /v1/files/{file_key}/meta",
  "removed_fields": [
    "url",
    "folder_name",
    "last_touched_at",
    "last_touched_by",
    "thumbnail_url",
    "creator",
    "role",
    "name",
    "version",
    "editorType",
    "link_access"
  ],
  "schema_path": "GET /v1/files/{file_key}/meta response 200"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Related changes

Other endpoints affected by the same root cause.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.