Skip to main content

Merge

This page contains the setup guide and reference information for the Merge source

Prerequisites

Access Token (which acts as bearer token) and linked accounts tokens are mandate for this connector to work, It could be seen at settings (Bearer ref - https://app.merge.dev/keys) and (Account token ref - https://app.merge.dev/keys).

Setup guide

Step 1: Set up Merge connection

  • Link your other integrations with account credentials on accounts section (ref - https://app.merge.dev/linked-accounts/accounts)
  • Get your bearer token on keys section (ref - https://app.merge.dev/keys)
  • Setup params (All params are required)
  • Available params
    • account_token: Linked account token seen after integration at linked account section
    • api_token: Bearer token seen at keys section, try to use production keys
    • start_date: Date filter for eligible streams

Step 2: Set up the Merge connector in Airbyte

For Airbyte Cloud:

  1. Log into your Airbyte Cloud account.
  2. In the left navigation bar, click Sources. In the top-right corner, click +new source.
  3. On the Set up the source page, enter the name for the merge connector and select Merge from the Source type dropdown.
  4. Enter your account_token, api_token and start_date.
  5. Click Set up source.

For Airbyte OSS:

  1. Navigate to the Airbyte Open Source dashboard.
  2. Set the name for your source.
  3. Enter your account_token, api_token and start_date.
  4. Click Set up source.

Supported sync modes

The Merge source connector supports the following sync modes:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncNo
Replicate Incremental DeletesNo
SSL connectionYes
NamespacesNo

Supported Streams

  • account_details
  • activities
  • applications
  • attachments
  • candidates
  • departments
  • eeocs
  • interviews
  • job-interview-stages
  • jobs
  • offers
  • offices
  • sync_status
  • users

API method example

GET https://api.merge.dev/api/ats/v1/account-details

Performance considerations

Merge API reference has v1 at present. The connector as default uses v1.

Reference

Config fields reference

Field
Type
Property name
string
account_token
string
api_token
string
start_date

Changelog

Expand to review
VersionDatePull RequestSubject
0.1.52024-07-0640932Update dependencies
0.1.42024-06-2540272Update dependencies
0.1.32024-06-2240163Update dependencies
0.1.22024-06-0639238[autopull] Upgrade base image to v1.2.2
0.1.12024-05-2038445[autopull] base image + poetry + up_to_date
0.1.02023-04-18InitInitial commit