Skip to content

Latest commit

 

History

History
71 lines (44 loc) · 2.81 KB

courier.md

File metadata and controls

71 lines (44 loc) · 2.81 KB
Raw

Courier

:::warning

Deprecation Notice

The Courier source connector is scheduled for deprecation on March 5th, 2024 due to incompatibility with upcoming platform updates as we prepare to launch Airbyte 1.0. This means it will no longer be supported or available for use in Airbyte.

This connector does not support new per-stream features which are vital for ensuring data integrity in Airbyte's synchronization processes. Without these capabilities, we cannot enforce our standards of reliability and correctness for data syncing operations.

Recommended Actions

Users who still wish to sync data from this connector are advised to explore creating a custom connector as an alternative to continue their data synchronization needs. For guidance, please visit our Custom Connector documentation.

:::

This page contains the setup guide and reference information for the Courier source connector.

Prerequisites

Generate an API key per the Courier documentation.

Setup guide

Step 1: Set up Courier

  • Courier Account
  • Courier API Key

Step 2: Set up the Courier 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 Courier connector and select Courier from the Source type dropdown.
  4. Enter your api_key.
  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 api_key.
  4. Click Set up source.

Supported sync modes

The Courier 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

  • Messages

Performance considerations

Courier's API reference does not address rate limiting but the connector implements exponential backoff when a 429 response status code is received.

Changelog

Version Date Pull Request Subject
0.1.0 2022-09-10 TODO Initial commit