New: MCP server monitoring is live. Start free trial
Hugging FaceSchemaBehavioral

Fields removed in POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users response 200: [repos]

Affected surface
POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users

What changed

Fields removed in POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users response 200: [repos] Affected surface: POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users. Root cause: endpoint `POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users`. Detected at Thu, 02 Jul 2026 07:03:54 UTC UTC.

Diff

{
  "path": "POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users",
  "removed_fields": [
    "repos"
  ],
  "schema_path": "POST /api/organizations/{name}/resource-groups/{resourceGroupId}/users 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.

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.