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

Response schema changed for GET /v1/employees/{employee_id}/onboarding_status (Employee-Onboarding-Status)

Affected surface
GET /v1/employees/{employee_id}/onboarding_status
Affected field
Employee-Onboarding-Status

What changed

Response schema changed for GET /v1/employees/{employee_id}/onboarding_status (Employee-Onboarding-Status) Affected surface: GET /v1/employees/{employee_id}/onboarding_status. Root cause: schema `Employee-Onboarding-Status`. Detected at Sat, 06 Jun 2026 04:26:55 UTC UTC.

Diff

{
  "added_fields": [
    "blockers"
  ],
  "path": "GET /v1/employees/{employee_id}/onboarding_status",
  "schema_path": "schema Employee-Onboarding-Status"
}

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.

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.