Skip to main content
PUT
/
companies
/
{companyId}
/
employees
/
{employeeId}
/
limits
/
recurrent
Set recurrent employee limits
curl --request PUT \
  --url https://pre-partners-api.cobee.io/api/v3/companies/{companyId}/employees/{employeeId}/limits/recurrent \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "meal": {
    "amount": {
      "amountInCents": 123,
      "currency": "EUR"
    },
    "appliesTo": "employee",
    "period": "payroll"
  },
  "transport": {
    "amount": {
      "amountInCents": 123,
      "currency": "EUR"
    },
    "appliesTo": "employee",
    "period": "payroll"
  },
  "nursery": {
    "amount": {
      "amountInCents": 123,
      "currency": "EUR"
    },
    "appliesTo": "employee",
    "period": "payroll"
  }
}
'
{
  "message": "Invalid employeeId"
}

Overview

This endpoint allows you to set the employee limits for all the benefits defined by the partner, such as meals, transport and nurseries. It is mandatory to send the field appliesTo for each benefit to specify if the limit applies to the employee or a child. The possible values are employee or child.

How it works?

The recurrent limit acts as the foundational base for an employee’s benefits month after month. It is tied to a specific payroll cycle using the payroll query parameter.
  • Next payroll cycle: You can only set recurrent limits for the next upcoming payroll cycle (e.g., if the current month is February, you must send March). Once set, this limit will automatically carry over into all subsequent payrolls.
  • Current or other future payroll cycles: If you attempt to update recurrent limits for the current payroll cycle or any cycle beyond the next one, the API will reject the request with a 422 Unprocessable Entity error.
  • Precedence: If an employee has a recurrent limit set, but a punctual limit is also set for the exact same month, the punctual limit will always prevail for that specific cycle.
If you need to make an adjustment for the current payroll cycle, please use the Punctual Limits endpoint instead.
For a detailed explanation of how limits work, including examples and scenarios, please refer to the Overview page.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

companyId
string<uuid>
required

The company identifier

employeeId
string
required

The employee identifier

Query Parameters

payroll
string
required

The next payroll cycle identifier (format YYYY-MM). It must strictly correspond to the next upcoming payroll cycle.

Body

application/json
meal
object
transport
object
nursery
object

Response

Limits successfully set