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

Schema reference changed in POST /v1/employees/{employee_id}/employee_benefits request body: "inline:object" → "Employee-Benefit-Create-Request"

Affected surface
POST /v1/employees/{employee_id}/employee_benefits

What changed

Schema reference changed in POST /v1/employees/{employee_id}/employee_benefits request body: "inline:object" → "Employee-Benefit-Create-Request" Affected surface: POST /v1/employees/{employee_id}/employee_benefits. Root cause: endpoint `POST /v1/employees/{employee_id}/employee_benefits`. Detected at Fri, 01 May 2026 00:37:23 UTC UTC.

Diff

{
  "current_value": "Employee-Benefit-Create-Request",
  "path": "POST /v1/employees/{employee_id}/employee_benefits",
  "previous_value": "inline:object",
  "schema_path": "POST /v1/employees/{employee_id}/employee_benefits request body"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

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.