Changelog
Back to All
Fixed

7d34dff82652ed2e7f6db178162c5beead1dbf08

27 days ago

PATCH /v3/applications/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/candidates/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/jobs/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/offers/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/openings/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/openings/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/rejection_details/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/users/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

PATCH /v3/users/{id}

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/applications

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/applications/{id}/reject

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/candidates

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/candidates/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/jobs

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/jobs/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/offers

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/openings

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/openings/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/users

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.

POST /v3/users/bulk

  • Fixed: A custom_fields value naming a select option ID that does not exist on the field now returns 422 Unprocessable Content listing the rejected IDs, instead of 403 Forbidden.