API CHANGE TRACKER / PagerDuty

PagerDuty breaking change: GET /v3/schedules/{id}/custom_shifts

removed the optional property `offset` from the response with the `200` status

Specification capture: . Published evidence last updated . This is captured contract evidence, not an observed outage or a result from scanning your code.

Which field and classification rule changed?

Changed field
offset
Rule ID
response.removed
Classifier version
2026-10-15.2
Direction
response
Finding ID
chg_d793881a54d1fbf31aea7b7f2ceea4071111652b62601ccfb0adbbfb3e2fc7a9

What is the recorded before and after evidence?

Previous specification SHA-256: 6c19f1f4b622e7d098e0a5a5f5ce04afdc0a21a5b9c1cb7b1649a594e88f2345

Revised specification SHA-256: 46bd6195063f262aef3b13de96e7c206d5c6f3e6aa79154c5655cce436b584db

Publisher version: 2.0.0 to 2.0.0.

  ...
  
      **`since` and `until` are required.**
+ 
+     Returns every custom shift that overlaps the window.
    operationId: listCustomShifts
    parameters:
  ...
        schema:
          type: string
-     - description: Start of time range (ISO 8601)
+     - description: |
+         Start of time range (ISO 8601). Can be at most 2 years in the future.
        example: 2026-06-01T00:00:00Z
        in: query
  ...
          format: date-time
          type: string
-     - description: End of time range (ISO 8601)
+     - description: |
+         End of time range (ISO 8601). Can be at most 2 years and 2 weeks in
+         the future.
        example: 2026-06-28T23:59:59Z
        in: query
  ...
          default: false
          type: boolean
-     - in: query
-       name: limit
-       schema:
-         default: 25
-         maximum: 100
-         minimum: 1
-         type: integer
-     - in: query
-       name: offset
-       schema:
-         default: 0
-         minimum: 0
-         type: integer

Inspect the complete release · Public source findings · Publisher specification source

How do I check whether this affects my code?

Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.

Check an authorized repository · Review coverage · Inspect classification rules