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

Security requirements changed for GET /v1/companies/{company_id}/employees/payment_details

Affected surface
GET /v1/companies/{company_id}/employees/payment_details

What changed

Security requirements changed for GET /v1/companies/{company_id}/employees/payment_details Affected surface: GET /v1/companies/{company_id}/employees/payment_details. Detected at Fri, 01 May 2026 00:37:23 UTC UTC.

Diff

{
  "current_value": [
    {
      "CompanyAccessAuth": null
    }
  ],
  "path": "GET /v1/companies/{company_id}/employees/payment_details",
  "previous_value": null
}

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.

Re-check your auth setup against the provider's current docs. Auth changes typically require config updates, not code changes.

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.