5c5e7a180e
* Add Courier connector * Add docs * Rename api key input + Cleanup fixtureS * Fix bad BearerAuthenticator param * Improve schemas * Fix schemas * Fix integrat testsg * solve conflict * redone some code * correct source * add seed config * auto-bump connector version * run format Co-authored-by: marcosmarxm <marcosmarxm@gmail.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
2.0 KiB
2.0 KiB
Courier
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:
- Log into your Airbyte Cloud account.
- In the left navigation bar, click Sources. In the top-right corner, click +new source.
- On the Set up the source page, enter the name for the Courier connector and select Courier from the Source type dropdown.
- Enter your
api_key. - Click Set up source.
For Airbyte OSS:
- Navigate to the Airbyte Open Source dashboard.
- Set the name for your source.
- Enter your
api_key. - 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 |