Schedules Listing and Details

Schedules Breaking Changes

Breaking changes

• /schedules/v1 List schedules

  • The schedule classification field in the list response has been renamed. Each schedule object in the content[] array now returns type and no longer returns kind.
  • What you must change: update your response parsing and any business logic that read content[].kind to read content[].type instead.

• /schedules/v1/{schedule_id} Get schedule details

  • The schedule classification field in the details response has been renamed. The response now returns type and no longer returns kind.
  • What you must change: update your response parsing and any business logic that read kind on the schedule resource to read type instead.

These endpoints let you list existing schedules and fetch a single schedule’s details so you can understand what is set to execute against a user’s consent. If you rely on the schedule classification to route or display schedules, using kind will now fail or return undefined. Switch to type everywhere you consume these responses.

Model updates

• The enum that defines the schedule classification has been renamed from ScheduleKind to ScheduleType.
  • What you must change: if you reference this schema in typed clients, validations, or database mappings, replace ScheduleKind with ScheduleType. This includes any switch statements or serializers that depended on the old model name.