Fixed
2026-02-13
7 months ago
PATCH /v3/applications/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/candidates/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/jobs/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/offers/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/openings/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/rejection_details/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
PATCH /v3/users/{id}
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/applications
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/applications/{id}/reject
- Fixed: Setting a deactivated user as the value of a
user-type rejection-question custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/candidates
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/jobs
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/offers
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/openings
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.
POST /v3/users
- Fixed: Setting a deactivated user as the value of a
user-type custom field now returns a 422 Unprocessable Content error instead of succeeding.