Parameter 'requestId' type changed from 'integer' to 'string' in PUT /api/v1/time_off/requests/{requestId}/status

What changed

Parameter 'requestId' type changed from 'integer' to 'string' in PUT /api/v1/time_off/requests/{requestId}/status Affected surface: PUT /api/v1/time_off/requests/{requestId}/status. Root cause: parameter `requestId@path`. Detected at Wed, 24 Jun 2026 06:02:12 UTC UTC.

Diff

{
  "current_value": "string",
  "parameter_in": "path",
  "parameter_name": "requestId",
  "path": "PUT /api/v1/time_off/requests/{requestId}/status",
  "previous_value": "integer"
}

Likely impact

Existing integrations relying on this surface will fail or behave incorrectly. Treat this as a release-blocker until the recommended action below is applied.

Recommended action

Audit serialization on both sides. Type changes break payloads silently more often than loudly — catch this in a contract test before it hits production.