Merge

Availability:

Airbyte Cloud Airbyte OSS PyAirbyte

Support Level:

Marketplace

Connector Version:

0.1.15(Last updated 2 days ago)

CDK Version:

1.0.0

Sync Success Rate:

Usage Rate:

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:

Feature	Supported?
Full Refresh Sync	Yes
Incremental Sync	No
Replicate Incremental Deletes	No
SSL connection	Yes
Namespaces	No

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

Version	Date	Pull Request	Subject
0.1.15	2024-08-24	44665	Update dependencies
0.1.14	2024-08-17	44297	Update dependencies
0.1.13	2024-08-12	43778	Update dependencies
0.1.12	2024-08-10	43661	Update dependencies
0.1.11	2024-08-03	43074	Update dependencies
0.1.10	2024-07-27	42645	Update dependencies
0.1.9	2024-07-20	42313	Update dependencies
0.1.8	2024-07-13	41862	Update dependencies
0.1.7	2024-07-10	41572	Update dependencies
0.1.6	2024-07-09	41246	Update dependencies
0.1.5	2024-07-06	40932	Update dependencies
0.1.4	2024-06-25	40272	Update dependencies
0.1.3	2024-06-22	40163	Update dependencies
0.1.2	2024-06-06	39238	[autopull] Upgrade base image to v1.2.2
0.1.1	2024-05-20	38445	[autopull] base image + poetry + up_to_date
0.1.0	2023-04-18	Init	Initial commit