Get contracts by person

This endpoint returns all contracts of an employee.

GET /api/v2/businesses/{businessId}/people/{personId}/contracts

If the request parameters —both businessId and personId— are correct, the response will include the list of contracts associated with the employee.

Response example

[
    {
        "from": "2026-01-15",
        "regularMinutes": 360,
        "weeklyContract": false,
        "dailyContract": true,
        "countingDays": "WEEKENDS_AND_HOLIDAYS",
        "additionalMinutes": 120,
        "regularControlPeriod": "YEARLY",
        "regularPeriodMultiplier": 1,
        "regularPeriodStartDate": "2026-01-15",
        "additionalControlPeriod": "YEARLY",
        "additionalPeriodMultiplier": 1,
        "additionalPeriodStartDate": "2026-01-15",
        "calendarDaysOff": true,
        "numberOfHolidays": 10,
        "numberOfPublicHolidays": 10,
        "weeklyDaysInvolved": "WEEKENDS_AND_HOLIDAYS",
        "costPerHour": 200.34,
        "personCategory": "AV",
        "employeeId": "0001",
        "completed": false
    }
]
Details

  • from: contract start date in yyyy-MM-dd format.

  • to: contract end date in yyyy-MM-dd format. This field is not returned if the contract is still active at the time of the request.

  • regularMinutes: regular hours (in minutes) established in the contract. The value is interpreted based on the defined time base: annual, weekly, or daily.

  • weeklyContract: whether the contract is defined weekly (true) or annually (false).

  • dailyContract: whether the contract is defined on a daily basis. If the contract is neither daily nor weekly, it is considered annual.

  • countingDays: for daily contracts, indicates which days are counted as working days. Possible values are MONDAY_SUNDAY, MONDAY_SATURDAY, LABOR_DAYS, LABOR_MONDAY_SATURDAY, or WEEKENDS_AND_HOLIDAYS.

  • additionalMinutes: additional hours (in minutes) established in the contract. The value is interpreted based on the defined time base: annual, weekly, or daily.

  • regularControlPeriod: control period for regular working hours. Possible values are WEEKLY, MONTHLY, YEARLY, or PERIODS.

  • regularPeriodMultiplier: multiplier index for the regularControlPeriod. For example, a value of 2 with a weekly control period would define a biweekly cycle.

  • regularPeriodStartDate: start date of the regularControlPeriod in yyyy-MM-dd format. This is only relevant if regularPeriodMultiplier is greater than 1; otherwise, it is ignored.

  • additionalControlPeriod: control period for additional hours. Possible values are WEEKLY, MONTHLY, YEARLY, or PERIODS.

  • additionalPeriodMultiplier: multiplier index for the additionalControlPeriod. For example, a value of 2 with a weekly control period would define a biweekly cycle.

  • additionalPeriodStartDate: start date of the additionalControlPeriod in yyyy-MM-dd format. This is only relevant if additionalPeriodMultiplier is greater than 1; otherwise, it is ignored.

  • calendarDaysOff: whether vacation days are processed as calendar days (true) or business days (false).

  • numberOfHolidays: number of vacation days included in the employee’s contract.

  • numberOfPublicHolidays: number of public holidays included in the employee’s contract.

  • weeklyDaysInvolved: working days of the week. Possible values are MONDAY_SUNDAY, MONDAY_SATURDAY, LABOR_DAYS, LABOR_MONDAY_SATURDAY, or WEEKENDS_AND_HOLIDAYS.

  • metadata: any additional data related to the contract that has been pre-configured. The structure of these metadata depends on the business configuration.

  • costPerHour: hourly cost of the employee.

  • personCategory: external identifier of the employee’s category.

  • employeeId: external identifier of the employee.

  • id: external identifier of the contract.

  • contractTypeName: name of the contract type applied.

  • completed: indicates whether the contract is finalized or not.

The response will include the data defined for each of the employee’s contracts. For example, if a contract type is not applied, the contractTypeName field will not appear in the response.

Considerations

If the employee has no contracts, the request will return an empty array [].

Error codes

This endpoint does not return any error codes of its own beyond those described in common errors.

Useful links

What is a contract? And a contract type?

How to apply a contract type?