Schema reference changed in POST /v1/companies/{company_id}/reports/employees_annual_fica_wage response 202: "inline:object" → "Employees-Annual-Fica-Wage-Rep…

What changed

Schema reference changed in POST /v1/companies/{company_id}/reports/employees_annual_fica_wage response 202: "inline:object" → "Employees-Annual-Fica-Wage-Report-Acceptance" Affected surface: POST /v1/companies/{company_id}/reports/employees_annual_fica_wage. Root cause: endpoint `POST /v1/companies/{company_id}/reports/employees_annual_fica_wage`. Detected at Sat, 30 May 2026 03:44:25 UTC UTC.

Diff

{
  "current_value": "Employees-Annual-Fica-Wage-Report-Acceptance",
  "path": "POST /v1/companies/{company_id}/reports/employees_annual_fica_wage",
  "previous_value": "inline:object",
  "schema_path": "POST /v1/companies/{company_id}/reports/employees_annual_fica_wage response 202"
}

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.

Recommended action

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