Skip to main content
GET
Preview merging two candidates

Authorizations

Authorization
string
header
required

Supabase JWT — Authorization: Bearer <token>.

Query Parameters

keep_id
string<uuid>
required

Candidate id (profile_interview.id) of the record that stays.

merge_id
string<uuid>
required

Candidate id (profile_interview.id) of the record merged into it (archived afterwards).

Response

The merge preview.

keep_id
string
required

Candidate id (profile_interview.id) of the record that stays.

merge_id
string
required

Candidate id (profile_interview.id) of the record merged into it.

fields
object[]
required

Each field the merge can take from either record, with both values. The kept record keeps its own value unless the merge chooses the other (field_choices).

skills
object
required

CV skills of both records.

attached_records
object
required

Applications, results, files, notes, tags and other records of each candidate. Everything of the merged record moves to the kept one.

blockers
object[]
required

Reasons the merge cannot run now. Empty when nothing blocks it.

can_merge
boolean
required

True when nothing blocks the merge and you may merge (owners and admins only).

preview_token
string
required

Send this value to merchant-candidate-merge. It changes when either record changes, so a merge only runs on the state shown here.

Example:

"9f2c1d..."