Changelog
Back to All
Removed

2026-08-18

about 1 month ago

GET /v3/applications

  • Added: rejection_reason_id on the response schema. References a /v3/rejection_reasons row scoped to the organization, and is null when the application was rejected without a reason or has not been rejected.

GET /v3/candidates

  • Fixed: phone_numbers, email_addresses, addresses, website_addresses and social_media_addresses now come back in the same order on every read of unchanged data, where entries sharing a sort position could previously shift between calls.

PATCH /v3/applications/{id}

  • Added: rejection_reason_id on the response schema. References a /v3/rejection_reasons row scoped to the organization, and is null when the application was rejected without a reason or has not been rejected.

PATCH /v3/candidates/{id}

  • Fixed: phone_numbers, email_addresses, addresses, website_addresses and social_media_addresses are returned in a consistent order, where entries sharing a sort position could previously vary.

PATCH /v3/candidates/{id}/anonymize

  • Fixed: phone_numbers, email_addresses, addresses, website_addresses and social_media_addresses are returned in a consistent order, where entries sharing a sort position could previously vary.

POST /v3/applications

  • Added: rejection_reason_id on the response schema. References a /v3/rejection_reasons row scoped to the organization, and is null when the application was rejected without a reason or has not been rejected.

POST /v3/applications/{id}/convert_to_candidate

  • Added: rejection_reason_id on the response schema. References a /v3/rejection_reasons row scoped to the organization, and is null when the application was rejected without a reason or has not been rejected.

POST /v3/applications/{id}/move

  • ⚠️ Breaking Fixed: email_from_user_id is now rejected with a 422 unless the caller is an integration service user.

POST /v3/applications/{id}/reject

  • ⚠️ Breaking Fixed: rejection_email.email_from_user_id is now rejected with a 422 unless the caller is an integration service user, and the referenced user must have an email address configured.

POST /v3/candidates

  • Fixed: phone_numbers, email_addresses, addresses, website_addresses and social_media_addresses are returned in a consistent order, where entries sharing a sort position could previously vary.

POST /v3/candidates/{id}/merge

  • Fixed: phone_numbers, email_addresses, addresses, website_addresses and social_media_addresses are returned in a consistent order, where entries sharing a sort position could previously vary.