Overview

Writing Data with Relations

Writing Nested Data

Related and Nested Writes

Write data to third-party platforms with relations to existing and new Common Model instances

Overview

Common Models sometimes have relationships with other Common Models.

For example:

  • Merge HRIS Employees can have related Employments
  • Merge ATS Candidates can have related Applications
  • Merge ATS Candidates can have related Attachments

Our POST endpoints allow you to:

  • Create relationships to existing entities through references to Merge ID’s
  • Create new related entities through nesting

You cannot create references to the Merge IDs of existing Common Model instances at the same time as a Nested Write.

Writing Data with Relations to Existing Data

When sending POST requests to Merge, related Common Model instances can be referenced by their Merge ID.

HRIS Example

When creating an Employee using our HRIS API, a relationship between an Employee and an existing Team can be created by adding the Merge ID of the relevant Team to the new Employee’s team field.

ATS Example

When creating an Attachment using our ATS API, a relationship between an Attachment and an existing Candidate is created by adding the Merge ID of the relevant Candidate to the new Attachment’s candidate field.

Writing Nested Data

Our POST endpoints allow you to create related Common Models in-line (also known as a Nested Write) if the related entity hasn’t been created yet.

HRIS Example

When creating an Employee using our HRIS API, to create a new related Employment within a new Employee, you would pass the details of the Employment in an object within the new Employee’s employments field.

ATS Example

When creating a Candidate using our ATS API, to create a new related Application within a new Candidate, you would pass the details of the Application in an object within the new Candidate’s applications field.

Previous
Writes
Next Up
Programmatic Writes with /meta