POST /workforce/resources/r1/resources/{resourceId}/qualifications/batch

Http Verb	POST
Url	/workforce/resources/r1/resources/{resourceId}/qualifications/batch
Permissions required	`RESOURCE_EDIT`:`fsm.core.resource.edit`
Personally Identifiable Information (PII)	No
Sensitive Information	No
Last Modified Version	r1
Released since	`2026 W3 (FSM 24.0)`
Deprecated since
Removed since
Tech Tags

Business Logic

This API associates a set of existing qualifications to a resource. If any check fails, an error is thrown and the execution stops.

Validations:

Resource is required and must exist
Qualification is required
Start date is required
End date is optional and if not omitted must be after start date; if omitted, the association is valid from the start date indefinitely
Associations with same resource/qualification/date-range cannot exists
If qualification-alignment (company.fsm.qualifications.enableAlignment) is enabled, it blocks changes for loan users with copyCompetences set to true.

Path Parameters

Field	Note
resourceId

Header Parameters

Default.

Request Body Parameters

Field	Validations	Note
qualificationId	Mandatory
startDate	Mandatory	The time is discarded and set to midnight because the validity field relates to the day, not the hour.
endDate		The time is discarded and set to midnight because the validity field relates to the day, not the hour. When setting a qualification end date to X via POST, send X + 1 day. This keeps API write/read behavior consistent. Why: in the database, end dates are stored as an exclusive upper bound at midnight. So, to represent validity for the full day of the 15th, we store 16th 00:00:00.

Field

Validations

Note

qualificationId

Mandatory

startDate

Mandatory

The time is discarded and set to midnight because the validity field relates to the day, not the hour.

endDate

The time is discarded and set to midnight because the validity field relates to the day, not the hour.

When setting a qualification end date to X via POST, send X + 1 day.
This keeps API write/read behavior consistent.
Why: in the database, end dates are stored as an exclusive upper bound at midnight.
So, to represent validity for the full day of the 15th, we store 16th 00:00:00.

Response documentation

Response error codes

BASE_0001, NOT_FOUND, BASE_0003, RESOURCE_011,