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

Response schema changed for GET /projects/{project_id}/branches/{branch_id}/auth/plugins/phone-number (NeonAuthPhoneNumberConfig)

Affected surface
GET /projects/{project_id}/branches/{branch_id}/auth/plugins/phone-number
Affected field
NeonAuthPhoneNumberConfig

What changed

Response schema changed for GET /projects/{project_id}/branches/{branch_id}/auth/plugins/phone-number (NeonAuthPhoneNumberConfig) Affected surface: GET /projects/{project_id}/branches/{branch_id}/auth/plugins/phone-number. Root cause: schema `NeonAuthPhoneNumberConfig`. Detected at Fri, 08 May 2026 00:52:37 UTC UTC.

Diff

{
  "path": "GET /projects/{project_id}/branches/{branch_id}/auth/plugins/phone-number",
  "removed_fields": [
    "allowed_attempts"
  ],
  "schema_path": "schema NeonAuthPhoneNumberConfig"
}

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.