Preview pay schedule dates
Changed onProvides a preview of a pay schedule with the specified parameters for the next 18 months. Use this before creating or updating a pay schedule to show expected check dates, pay period boundaries, and payroll deadlines.
Related guides
- Create a pay schedule
- Manage Pay Schedules via API
scope: pay_schedules:write
Request
- Base URLhttps://api.gusto-demo.com
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
The UUID of the company
Query parameters
The frequency that employees on this pay schedule are paid with Gusto.
The first date that employees on this pay schedule are paid with Gusto.
The last date of the first pay period. This can be the same date as the anchor pay date.
Legacy field, retained unchanged for compatibility. The first pay day for Monthly and regular Twice per month schedules, or the first pay-period end day for flexible Twice per month schedules. Prefer the explicit pay-period fields. Do not combine day_1/day_2 with explicit fields in a request.
Legacy field, retained unchanged for compatibility. The second pay day for regular Twice per month schedules, or the second pay-period end day for flexible Twice per month schedules. A value of 31 means the last day of the month. Prefer the explicit pay-period fields. Do not combine day_1/day_2 with explicit fields in a request.
The first pay day (1-31) for Monthly or Twice per month. For Twice per month, provide both pay-day fields together. Pay days alone configure a regular schedule; adding both explicit period-end days configures a flexible schedule. Omitted fields preserve existing values on update or persisted preview. Pay days on an existing flexible schedule cannot both be cleared. Do not mix explicit fields with day_1/day_2.
The second pay day (1-31) for Twice per month. Provide both pay-day fields together. Pay days alone configure a regular schedule; adding both explicit period-end days configures a flexible schedule. Omitted fields preserve existing values on update or persisted preview. Pay days on an existing flexible schedule cannot both be cleared. A pay day may fall in the following month. Do not mix explicit fields with day_1/day_2.
The last day (1-31) of the first pay period for a flexible Twice per month schedule. On create or conversion, both explicit period-end days are required. On an existing flexible schedule, omitted values are preserved and changing them requires a matching anchor_end_of_pay_period and anchor_pay_date. Do not mix explicit fields with day_1/day_2.
The last day (1-31) of the second pay period for a flexible Twice per month schedule. A value of 31 means the last day of the month. On create or conversion, both explicit period-end days are required. On an existing flexible schedule, omitted values are preserved and changing them requires a matching anchor_end_of_pay_period and anchor_pay_date. Do not mix explicit fields with day_1/day_2.
End date for the preview range. If given, this date must be in the future. When unspecified, defaults to 18 months from today.
Optional UUID of an existing pay schedule. When supplied, the preview is seeded from the persisted schedule — including internal flags (such as arrears handling) that affect period boundaries but are not exposed as request parameters. Any other query parameters override individual attributes on top of the loaded schedule.
Headers
Determines the date-based API version associated with your API call. If none is provided, your application's minimum API version is used.
Response
Successful
Changes
- info
added the new optional
queryrequest parameterfirst_pay_period_end_day - info
added the new optional
queryrequest parameterfirst_pay_period_pay_day - info
added the new optional
queryrequest parametersecond_pay_period_end_day - info
added the new optional
queryrequest parametersecond_pay_period_pay_day - info
queryrequest parameterday_1was deprecated - info
queryrequest parameterday_2was deprecated
- info