From 5512befeb1ac2c1d3348dd20df0ed31b11e1c4d3 Mon Sep 17 00:00:00 2001 From: Sophia Wiley <106352739+sophia-wiley@users.noreply.github.com> Date: Mon, 6 Mar 2023 08:27:55 -0800 Subject: [PATCH] Docs: updated links from .io to .com (#23652) * updated links * edited contributors link * deleted line about CDK in docs --- docs/archive/changelog/README.md | 2 +- docs/archive/changelog/connectors.md | 252 +++++++++--------- docs/archive/changelog/platform.md | 4 +- .../build-a-slack-activity-dashboard.md | 4 +- docs/archive/examples/slack-history.md | 2 +- .../examples/zoom-activity-dashboard.md | 4 +- .../differences-with/fivetran-vs-airbyte.md | 4 +- .../differences-with/meltano-vs-airbyte.md | 6 +- .../faq/differences-with/singer-vs-airbyte.md | 6 +- .../differences-with/stitchdata-vs-airbyte.md | 4 +- docs/cloud/core-concepts.md | 2 +- .../getting-started-with-airbyte-cloud.md | 2 +- docs/cloud/managing-airbyte-cloud.md | 22 +- .../edit-stream-configuration.md | 2 +- .../manage-airbyte-cloud-notifications.md | 2 +- .../manage-airbyte-cloud-workspace.md | 10 +- .../manage-data-residency.md | 4 +- .../review-connection-state.md | 2 +- .../review-sync-summary.md | 2 +- .../cdk-python/incremental-stream.md | 2 +- .../3-connecting-to-the-API-source.md | 6 +- .../config-based/tutorial/4-reading-data.md | 4 +- .../tutorial/5-incremental-reads.md | 4 +- .../tutorials/adding-incremental-sync.md | 2 +- .../build-a-connector-the-hard-way.md | 6 +- .../tutorials/building-a-java-destination.md | 2 +- .../building-a-python-destination.md | 4 +- .../tutorials/cdk-speedrun-deprecated.md | 2 +- .../tutorials/cdk-speedrun.md | 6 +- .../declare-schema.md | 2 +- .../cdk-tutorial-python-http/define-inputs.md | 4 +- docs/connector-development/ux-handbook.md | 4 +- docs/contributing-to-airbyte/README.md | 2 +- docs/deploying-airbyte/on-cloud.md | 2 +- docs/integrations/destinations/bigquery.md | 4 +- docs/integrations/destinations/chargify.md | 2 +- docs/integrations/destinations/databricks.md | 2 +- docs/integrations/destinations/gcs.md | 4 +- .../destinations/google-sheets.md | 2 +- docs/integrations/destinations/kafka.md | 2 +- docs/integrations/destinations/mqtt.md | 2 +- docs/integrations/destinations/postgres.md | 2 +- docs/integrations/destinations/pulsar.md | 2 +- docs/integrations/destinations/r2.md | 6 +- docs/integrations/destinations/redshift.md | 2 +- docs/integrations/destinations/s3-glue.md | 2 +- docs/integrations/destinations/s3.md | 6 +- docs/integrations/sources/airtable.md | 2 +- docs/integrations/sources/alloydb.md | 2 +- docs/integrations/sources/amazon-ads.md | 2 +- .../sources/amazon-seller-partner.md | 2 +- docs/integrations/sources/amplitude.md | 2 +- docs/integrations/sources/appfollow.md | 2 +- docs/integrations/sources/asana.md | 2 +- docs/integrations/sources/bamboo-hr.md | 2 +- docs/integrations/sources/bigcommerce.md | 2 - docs/integrations/sources/bing-ads.md | 2 +- docs/integrations/sources/braze.md | 2 +- docs/integrations/sources/chargebee.md | 2 +- docs/integrations/sources/chartmogul.md | 2 +- docs/integrations/sources/close-com.md | 2 +- docs/integrations/sources/coda.md | 2 +- docs/integrations/sources/commcare.md | 4 +- docs/integrations/sources/commercetools.md | 2 - docs/integrations/sources/courier.md | 2 +- docs/integrations/sources/datadog.md | 2 +- docs/integrations/sources/datascope.md | 4 +- docs/integrations/sources/delighted.md | 2 +- docs/integrations/sources/dremio.md | 2 - .../sources/facebook-marketing.md | 2 +- docs/integrations/sources/facebook-pages.md | 2 +- docs/integrations/sources/fastbill.md | 4 +- docs/integrations/sources/freshdesk.md | 2 +- docs/integrations/sources/github.md | 2 +- docs/integrations/sources/gitlab.md | 2 +- docs/integrations/sources/glassfrog.md | 2 +- docs/integrations/sources/google-ads.md | 2 +- .../sources/google-analytics-data-api.md | 2 +- .../sources/google-analytics-v4.md | 2 +- .../sources/google-pagespeed-insights.md | 2 +- .../sources/google-search-console.md | 2 +- docs/integrations/sources/google-sheets.md | 2 +- docs/integrations/sources/google-webfonts.md | 4 +- docs/integrations/sources/greenhouse.md | 2 +- docs/integrations/sources/gutendex.md | 2 +- docs/integrations/sources/harvest.md | 2 +- docs/integrations/sources/hubspot.md | 2 +- docs/integrations/sources/insightly.md | 2 +- docs/integrations/sources/instagram.md | 2 +- docs/integrations/sources/intercom.md | 2 +- docs/integrations/sources/iterable.md | 2 +- docs/integrations/sources/jira.md | 2 +- docs/integrations/sources/klaviyo.md | 2 +- docs/integrations/sources/linkedin-ads.md | 2 +- docs/integrations/sources/linkedin-pages.md | 6 +- docs/integrations/sources/linnworks.md | 2 +- docs/integrations/sources/lokalise.md | 2 +- docs/integrations/sources/mailchimp.md | 2 +- docs/integrations/sources/marketo.md | 2 +- docs/integrations/sources/mixpanel.md | 2 +- docs/integrations/sources/monday.md | 2 +- docs/integrations/sources/netsuite.md | 2 +- docs/integrations/sources/notion.md | 2 +- docs/integrations/sources/okta.md | 2 +- .../sources/paypal-transaction.md | 2 +- docs/integrations/sources/pexels-api.md | 2 +- docs/integrations/sources/pinterest.md | 2 +- docs/integrations/sources/postgres.md | 2 +- docs/integrations/sources/posthog.md | 2 +- docs/integrations/sources/postmarkapp.md | 4 +- docs/integrations/sources/prestashop.md | 2 +- docs/integrations/sources/punk-api.md | 4 +- docs/integrations/sources/qualaroo.md | 2 - docs/integrations/sources/railz.md | 2 +- docs/integrations/sources/recharge.md | 2 +- docs/integrations/sources/recruitee.md | 2 +- docs/integrations/sources/s3.md | 2 +- docs/integrations/sources/salesforce.md | 2 +- docs/integrations/sources/search-metrics.md | 2 - docs/integrations/sources/sendgrid.md | 2 +- docs/integrations/sources/senseforce.md | 2 +- docs/integrations/sources/sentry.md | 2 +- docs/integrations/sources/sftp.md | 2 +- docs/integrations/sources/shopify.md | 2 - docs/integrations/sources/shortio.md | 2 - docs/integrations/sources/slack.md | 2 +- docs/integrations/sources/smartsheets.md | 2 +- .../sources/snapchat-marketing.md | 2 +- docs/integrations/sources/spacex-api.md | 2 +- docs/integrations/sources/square.md | 2 +- docs/integrations/sources/stripe.md | 2 +- docs/integrations/sources/surveycto.md | 2 +- docs/integrations/sources/surveymonkey.md | 2 +- docs/integrations/sources/tempo.md | 2 +- docs/integrations/sources/the-guardian-api.md | 2 +- docs/integrations/sources/tiktok-marketing.md | 2 +- docs/integrations/sources/tmdb.md | 4 +- docs/integrations/sources/tplcentral.md | 2 - docs/integrations/sources/trello.md | 2 - .../integrations/sources/twilio-taskrouter.md | 2 +- docs/integrations/sources/twilio.md | 2 +- docs/integrations/sources/tyntec-sms.md | 4 +- docs/integrations/sources/typeform.md | 2 +- docs/integrations/sources/visma-economic.md | 4 +- docs/integrations/sources/waiteraid.md | 2 +- .../sources/wikipedia-pageviews.md | 4 +- docs/integrations/sources/woocommerce.md | 2 +- docs/integrations/sources/workable.md | 2 +- docs/integrations/sources/wrike.md | 2 +- .../integrations/sources/youtube-analytics.md | 2 +- docs/integrations/sources/zendesk-chat.md | 2 +- docs/integrations/sources/zendesk-support.md | 2 +- docs/integrations/sources/zendesk-talk.md | 2 +- docs/integrations/sources/zenloop.md | 2 +- docs/integrations/sources/zoho-crm.md | 2 - docs/integrations/sources/zuora.md | 2 - docs/reference/api/README.md | 2 +- 157 files changed, 324 insertions(+), 346 deletions(-) diff --git a/docs/archive/changelog/README.md b/docs/archive/changelog/README.md index 887369c805d2..6fae211dd8ee 100644 --- a/docs/archive/changelog/README.md +++ b/docs/archive/changelog/README.md @@ -438,7 +438,7 @@ New Destination: Keen * 🐛 Shopify source: Fixed the `products` schema to be in accordance with the API. * 🐛 S3 source: Fixed bug where syncs could hang indefinitely. -And as always... we'd love to shout out the awesome contributors that have helped push Airbyte forward. As a reminder, you can now see your contributions publicly reflected on our [contributors page](https://airbyte.io/contributors). +And as always... we'd love to shout out the awesome contributors that have helped push Airbyte forward. As a reminder, you can now see your contributions publicly reflected on our [contributors page](https://airbyte.com/contributors). Thank you to Rodrigo Parra, Brian Krausz, Max Krog, Apostol Tegko, Matej Hamas, Vladimir Remar, Marco Fontana, Nicholas Bull, @mildbyte, @subhaklp, and Maciej Nędza! diff --git a/docs/archive/changelog/connectors.md b/docs/archive/changelog/connectors.md index 2d597c74fa2d..0e519ea7b76e 100644 --- a/docs/archive/changelog/connectors.md +++ b/docs/archive/changelog/connectors.md @@ -14,57 +14,57 @@ Check out our [connector roadmap](https://github.com/airbytehq/airbyte/projects/ New sources: -- [**Chartmogul**](https://docs.airbyte.io/integrations/sources/chartmogul) -- [**Hellobaton**](https://docs.airbyte.io/integrations/sources/hellobaton) -- [**Flexport**](https://docs.airbyte.io/integrations/sources/flexport) -- [**PersistIq**](https://docs.airbyte.io/integrations/sources/persistiq) +- [**Chartmogul**](https://docs.airbyte.com/integrations/sources/chartmogul) +- [**Hellobaton**](https://docs.airbyte.com/integrations/sources/hellobaton) +- [**Flexport**](https://docs.airbyte.com/integrations/sources/flexport) +- [**PersistIq**](https://docs.airbyte.com/integrations/sources/persistiq) ## 1/6/2022 New sources: -- [**3PL Central**](https://docs.airbyte.io/integrations/sources/tplcentral) -- [**My Hours**](https://docs.airbyte.io/integrations/sources/my-hours) -- [**Qualaroo**](https://docs.airbyte.io/integrations/sources/qualaroo) -- [**SearchMetrics**](https://docs.airbyte.io/integrations/sources/search-metrics) +- [**3PL Central**](https://docs.airbyte.com/integrations/sources/tplcentral) +- [**My Hours**](https://docs.airbyte.com/integrations/sources/my-hours) +- [**Qualaroo**](https://docs.airbyte.com/integrations/sources/qualaroo) +- [**SearchMetrics**](https://docs.airbyte.com/integrations/sources/search-metrics) ## 12/16/2021 New source: -- [**OpenWeather**](https://docs.airbyte.io/integrations/sources/openweather) +- [**OpenWeather**](https://docs.airbyte.com/integrations/sources/openweather) New destinations: -- [**ClickHouse**](https://docs.airbyte.io/integrations/destinations/clickhouse) -- [**RabbitMQ**](https://docs.airbyte.io/integrations/destinations/rabbitmq) -- [**Amazon SQS**](https://docs.airbyte.io/integrations/destinations/amazon-sqs) -- [**Rockset**](https://docs.airbyte.io/integrations/destinations/rockset) +- [**ClickHouse**](https://docs.airbyte.com/integrations/destinations/clickhouse) +- [**RabbitMQ**](https://docs.airbyte.com/integrations/destinations/rabbitmq) +- [**Amazon SQS**](https://docs.airbyte.com/integrations/destinations/amazon-sqs) +- [**Rockset**](https://docs.airbyte.com/integrations/destinations/rockset) ## 12/9/2021 New source: -- [**Mailgun**](https://docs.airbyte.io/integrations/sources/mailgun) +- [**Mailgun**](https://docs.airbyte.com/integrations/sources/mailgun) ## 12/2/2021 New destinations: -- [**Redis**](https://docs.airbyte.io/integrations/destinations/redis) -- [**MQTT**](https://docs.airbyte.io/integrations/destinations/mqtt) -- [**Google Firestore**](https://docs.airbyte.io/integrations/destinations/google-firestore) -- [**Kinesis**](https://docs.airbyte.io/integrations/destinations/kinesis) +- [**Redis**](https://docs.airbyte.com/integrations/destinations/redis) +- [**MQTT**](https://docs.airbyte.com/integrations/destinations/mqtt) +- [**Google Firestore**](https://docs.airbyte.com/integrations/destinations/google-firestore) +- [**Kinesis**](https://docs.airbyte.com/integrations/destinations/kinesis) ## 11/25/2021 New sources: -- [**Airtable**](https://docs.airbyte.io/integrations/sources/airtable) -- [**Notion**](https://docs.airbyte.io/integrations/sources/notion) -- [**Pardot**](https://docs.airbyte.io/integrations/sources/pardot) -- [**Notion**](https://docs.airbyte.io/integrations/sources/linnworks) -- [**YouTube Analytics**](https://docs.airbyte.io/integrations/sources/youtube-analytics) +- [**Airtable**](https://docs.airbyte.com/integrations/sources/airtable) +- [**Notion**](https://docs.airbyte.com/integrations/sources/notion) +- [**Pardot**](https://docs.airbyte.com/integrations/sources/pardot) +- [**Notion**](https://docs.airbyte.com/integrations/sources/linnworks) +- [**YouTube Analytics**](https://docs.airbyte.com/integrations/sources/youtube-analytics) New features: @@ -81,12 +81,12 @@ New features: New destination: -- [**ScyllaDB**](https://docs.airbyte.io/integrations/destinations/scylla) +- [**ScyllaDB**](https://docs.airbyte.com/integrations/destinations/scylla) New sources: -- [**Azure Table Storage**](https://docs.airbyte.io/integrations/sources/azure-table) -- [**Linnworks**](https://docs.airbyte.io/integrations/sources/linnworks) +- [**Azure Table Storage**](https://docs.airbyte.com/integrations/sources/azure-table) +- [**Linnworks**](https://docs.airbyte.com/integrations/sources/linnworks) New features: @@ -97,15 +97,15 @@ New features: New destinations: -- [**Cassandra**](https://docs.airbyte.io/integrations/destinations/cassandra) -- [**Pulsar**](https://docs.airbyte.io/integrations/destinations/pulsar) +- [**Cassandra**](https://docs.airbyte.com/integrations/destinations/cassandra) +- [**Pulsar**](https://docs.airbyte.com/integrations/destinations/pulsar) New sources: -- [**Confluence**](https://docs.airbyte.io/integrations/sources/confluence) -- [**Monday**](https://docs.airbyte.io/integrations/sources/monday) +- [**Confluence**](https://docs.airbyte.com/integrations/sources/confluence) +- [**Monday**](https://docs.airbyte.com/integrations/sources/monday) - [**Commerce Tools**](https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-commercetools) -- [**Pinterest**](https://docs.airbyte.io/integrations/sources/pinterest) +- [**Pinterest**](https://docs.airbyte.com/integrations/sources/pinterest) New features: @@ -119,20 +119,20 @@ New features: New destination: -- [**Elasticsearch**](https://docs.airbyte.io/integrations/destinations/elasticsearch) +- [**Elasticsearch**](https://docs.airbyte.com/integrations/destinations/elasticsearch) New sources: -- [**Salesloft**](https://docs.airbyte.io/integrations/sources/salesloft) -- [**OneSignal**](https://docs.airbyte.io/integrations/sources/onesignal) -- [**Strava**](https://docs.airbyte.io/integrations/sources/strava) -- [**Lemlist**](https://docs.airbyte.io/integrations/sources/lemlist) -- [**Amazon SQS**](https://docs.airbyte.io/integrations/sources/amazon-sqs) -- [**Freshservices**](https://docs.airbyte.io/integrations/source/freshservices) -- [**Freshsales**](https://docs.airbyte.io/integrations/sources/freshsales) +- [**Salesloft**](https://docs.airbyte.com/integrations/sources/salesloft) +- [**OneSignal**](https://docs.airbyte.com/integrations/sources/onesignal) +- [**Strava**](https://docs.airbyte.com/integrations/sources/strava) +- [**Lemlist**](https://docs.airbyte.com/integrations/sources/lemlist) +- [**Amazon SQS**](https://docs.airbyte.com/integrations/sources/amazon-sqs) +- [**Freshservices**](https://docs.airbyte.com/integrations/source/freshservices) +- [**Freshsales**](https://docs.airbyte.com/integrations/sources/freshsales) - [**Appsflyer**](https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-appsflyer) -- [**Paystack**](https://docs.airbyte.io/integrations/sources/paystack) -- [**Sentry**](https://docs.airbyte.io/integrations/sources/sentry) +- [**Paystack**](https://docs.airbyte.com/integrations/sources/paystack) +- [**Sentry**](https://docs.airbyte.com/integrations/sources/sentry) - [**Retently**](https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-retently) - [**Delighted!**](https://github.com/airbytehq/airbyte/tree/master/airbyte-integrations/connectors/source-delighted) @@ -147,7 +147,7 @@ New features: New source: -- [**WooCommerce**](https://docs.airbyte.io/integrations/sources/woocommerce) +- [**WooCommerce**](https://docs.airbyte.com/integrations/sources/woocommerce) New feature: @@ -157,9 +157,9 @@ New feature: New sources: -- [**LinkedIn Ads**](https://docs.airbyte.io/integrations/sources/linkedin-ads) -- [**Kafka**](https://docs.airbyte.io/integrations/sources/kafka) -- [**Lever Hiring**](https://docs.airbyte.io/integrations/sources/lever-hiring) +- [**LinkedIn Ads**](https://docs.airbyte.com/integrations/sources/linkedin-ads) +- [**Kafka**](https://docs.airbyte.com/integrations/sources/kafka) +- [**Lever Hiring**](https://docs.airbyte.com/integrations/sources/lever-hiring) New features: @@ -178,12 +178,12 @@ New features: New destinations: -- [**Databricks**](https://docs.airbyte.io/integrations/destinations/databricks) +- [**Databricks**](https://docs.airbyte.com/integrations/destinations/databricks) New sources: -- [**Close.com**](https://docs.airbyte.io/integrations/sources/close-com) -- [**Google Search Console**](https://docs.airbyte.io/integrations/sources/google-search-console) +- [**Close.com**](https://docs.airbyte.com/integrations/sources/close-com) +- [**Google Search Console**](https://docs.airbyte.com/integrations/sources/google-search-console) New features: @@ -201,12 +201,12 @@ New features: New source: -- [**Facebook Pages**](https://docs.airbyte.io/integrations/sources/facebook-pages) +- [**Facebook Pages**](https://docs.airbyte.com/integrations/sources/facebook-pages) New destinations: -- [**MongoDB**](https://docs.airbyte.io/integrations/destinations/mongodb) -- [**DynamoDB**](https://docs.airbyte.io/integrations/destinations/dynamodb) +- [**MongoDB**](https://docs.airbyte.com/integrations/destinations/mongodb) +- [**DynamoDB**](https://docs.airbyte.com/integrations/destinations/dynamodb) New features: @@ -236,11 +236,11 @@ Bug fixes: New sources: -- [**Bamboo HR**](https://docs.airbyte.io/integrations/sources/bamboo-hr) -- [**BigCommerce**](https://docs.airbyte.io/integrations/sources/bigcommerce) -- [**Trello**](https://docs.airbyte.io/integrations/sources/trello) -- [**Google Analytics V4**](https://docs.airbyte.io/integrations/sources/google-analytics-v4) -- [**Amazon Ads**](https://docs.airbyte.io/integrations/sources/google-analytics-v4) +- [**Bamboo HR**](https://docs.airbyte.com/integrations/sources/bamboo-hr) +- [**BigCommerce**](https://docs.airbyte.com/integrations/sources/bigcommerce) +- [**Trello**](https://docs.airbyte.com/integrations/sources/trello) +- [**Google Analytics V4**](https://docs.airbyte.com/integrations/sources/google-analytics-v4) +- [**Amazon Ads**](https://docs.airbyte.com/integrations/sources/google-analytics-v4) Bug fixes: @@ -250,7 +250,7 @@ Bug fixes: New source: -- [**Short.io**](https://docs.airbyte.io/integrations/sources/shortio) +- [**Short.io**](https://docs.airbyte.com/integrations/sources/shortio) New features: @@ -267,11 +267,11 @@ Bug fixes: New source: -- [**Bing Ads**](https://docs.airbyte.io/integrations/sources/bing-ads) +- [**Bing Ads**](https://docs.airbyte.com/integrations/sources/bing-ads) New destination: -- [**Keen**](https://docs.airbyte.io/integrations/destinations/keen) +- [**Keen**](https://docs.airbyte.com/integrations/destinations/keen) New features: @@ -289,11 +289,11 @@ Bug fixes: New sources: -- [**S3/Abstract Files**](https://docs.airbyte.io/integrations/sources/s3) -- [**Zuora**](https://docs.airbyte.io/integrations/sources/zuora) -- [**Kustomer**](https://docs.airbyte.io/integrations/sources/kustomer) -- [**Apify**](https://docs.airbyte.io/integrations/sources/apify-dataset) -- [**Chargebee**](https://docs.airbyte.io/integrations/sources/chargebee) +- [**S3/Abstract Files**](https://docs.airbyte.com/integrations/sources/s3) +- [**Zuora**](https://docs.airbyte.com/integrations/sources/zuora) +- [**Kustomer**](https://docs.airbyte.com/integrations/sources/kustomer) +- [**Apify**](https://docs.airbyte.com/integrations/sources/apify-dataset) +- [**Chargebee**](https://docs.airbyte.com/integrations/sources/chargebee) New features: @@ -322,22 +322,22 @@ New CDK features: New sources: -- [**PrestaShop**](https://docs.airbyte.io/integrations/sources/prestashop) -- [**Snapchat Marketing**](https://docs.airbyte.io/integrations/sources/snapchat-marketing) -- [**Drupal**](https://docs.airbyte.io/integrations/sources/drupal) -- [**Magento**](https://docs.airbyte.io/integrations/sources/magento) -- [**Microsoft Dynamics AX**](https://docs.airbyte.io/integrations/sources/microsoft-dynamics-ax) -- [**Microsoft Dynamics Customer Engagement**](https://docs.airbyte.io/integrations/sources/microsoft-dynamics-customer-engagement) -- [**Microsoft Dynamics GP**](https://docs.airbyte.io/integrations/sources/microsoft-dynamics-gp) -- [**Microsoft Dynamics NAV**](https://docs.airbyte.io/integrations/sources/microsoft-dynamics-nav) -- [**Oracle PeopleSoft**](https://docs.airbyte.io/integrations/sources/oracle-peoplesoft) -- [**Oracle Siebel CRM**](https://docs.airbyte.io/integrations/sources/oracle-siebel-crm) -- [**SAP Business One**](https://docs.airbyte.io/integrations/sources/sap-business-one) -- [**Spree Commerce**](https://docs.airbyte.io/integrations/sources/spree-commerce) -- [**Sugar CRM**](https://docs.airbyte.io/integrations/sources/sugar-crm) -- [**WooCommerce**](https://docs.airbyte.io/integrations/sources/woocommerce) -- [**Wordpress**](https://docs.airbyte.io/integrations/sources/wordpress) -- [**Zencart**](https://docs.airbyte.io/integrations/sources/zencart) +- [**PrestaShop**](https://docs.airbyte.com/integrations/sources/prestashop) +- [**Snapchat Marketing**](https://docs.airbyte.com/integrations/sources/snapchat-marketing) +- [**Drupal**](https://docs.airbyte.com/integrations/sources/drupal) +- [**Magento**](https://docs.airbyte.com/integrations/sources/magento) +- [**Microsoft Dynamics AX**](https://docs.airbyte.com/integrations/sources/microsoft-dynamics-ax) +- [**Microsoft Dynamics Customer Engagement**](https://docs.airbyte.com/integrations/sources/microsoft-dynamics-customer-engagement) +- [**Microsoft Dynamics GP**](https://docs.airbyte.com/integrations/sources/microsoft-dynamics-gp) +- [**Microsoft Dynamics NAV**](https://docs.airbyte.com/integrations/sources/microsoft-dynamics-nav) +- [**Oracle PeopleSoft**](https://docs.airbyte.com/integrations/sources/oracle-peoplesoft) +- [**Oracle Siebel CRM**](https://docs.airbyte.com/integrations/sources/oracle-siebel-crm) +- [**SAP Business One**](https://docs.airbyte.com/integrations/sources/sap-business-one) +- [**Spree Commerce**](https://docs.airbyte.com/integrations/sources/spree-commerce) +- [**Sugar CRM**](https://docs.airbyte.com/integrations/sources/sugar-crm) +- [**WooCommerce**](https://docs.airbyte.com/integrations/sources/woocommerce) +- [**Wordpress**](https://docs.airbyte.com/integrations/sources/wordpress) +- [**Zencart**](https://docs.airbyte.com/integrations/sources/zencart) Bug fixes: @@ -349,14 +349,14 @@ Bug fixes: New sources: -- [**Pipedrive**](https://docs.airbyte.io/integrations/sources/pipedrive) -- [**US Census**](https://docs.airbyte.io/integrations/sources/us-census) -- [**BigQuery**](https://docs.airbyte.io/integrations/sources/bigquery) +- [**Pipedrive**](https://docs.airbyte.com/integrations/sources/pipedrive) +- [**US Census**](https://docs.airbyte.com/integrations/sources/us-census) +- [**BigQuery**](https://docs.airbyte.com/integrations/sources/bigquery) New destinations: -- [**Google Cloud Storage**](https://docs.airbyte.io/integrations/destinations/gcs) -- [**Kafka**](https://docs.airbyte.io/integrations/destinations/kafka) +- [**Google Cloud Storage**](https://docs.airbyte.com/integrations/destinations/gcs) +- [**Kafka**](https://docs.airbyte.com/integrations/destinations/kafka) New Features: @@ -379,9 +379,9 @@ Bug Fixes: 3 new sources: -- [**Zendesk Sunshine**](https://docs.airbyte.io/integrations/sources/zendesk-sunshine) -- [**Dixa**](https://docs.airbyte.io/integrations/sources/dixa) -- [**Typeform**](https://docs.airbyte.io/integrations/sources/typeform) +- [**Zendesk Sunshine**](https://docs.airbyte.com/integrations/sources/zendesk-sunshine) +- [**Dixa**](https://docs.airbyte.com/integrations/sources/dixa) +- [**Typeform**](https://docs.airbyte.com/integrations/sources/typeform) New Features: @@ -399,13 +399,13 @@ Bug Fixes: 7 new sources: -- [**PayPal Transaction**](https://docs.airbyte.io/integrations/sources/paypal-transaction) -- [**Square**](https://docs.airbyte.io/integrations/sources/square) -- [**SurveyMonkey**](https://docs.airbyte.io/integrations/sources/surveymonkey) -- [**CockroachDB**](https://docs.airbyte.io/integrations/sources/cockroachdb) -- [**Airbyte-native GitLab**](https://docs.airbyte.io/integrations/sources/gitlab) -- [**Airbyte-native GitHub**](https://docs.airbyte.io/integrations/sources/github) -- [**Airbyte-native Twilio**](https://docs.airbyte.io/integrations/sources/twilio) +- [**PayPal Transaction**](https://docs.airbyte.com/integrations/sources/paypal-transaction) +- [**Square**](https://docs.airbyte.com/integrations/sources/square) +- [**SurveyMonkey**](https://docs.airbyte.com/integrations/sources/surveymonkey) +- [**CockroachDB**](https://docs.airbyte.com/integrations/sources/cockroachdb) +- [**Airbyte-native GitLab**](https://docs.airbyte.com/integrations/sources/gitlab) +- [**Airbyte-native GitHub**](https://docs.airbyte.com/integrations/sources/github) +- [**Airbyte-native Twilio**](https://docs.airbyte.com/integrations/sources/twilio) New Features: @@ -441,7 +441,7 @@ Bugfixes: 1 new source: -- [**Db2**](https://docs.airbyte.io/integrations/sources/db2) +- [**Db2**](https://docs.airbyte.com/integrations/sources/db2) New features: @@ -454,7 +454,7 @@ New features: 1 new source: -- [**Snowflake**](https://docs.airbyte.io/integrations/sources/snowflake) +- [**Snowflake**](https://docs.airbyte.com/integrations/sources/snowflake) New features: @@ -468,13 +468,13 @@ New features: 1 new destination: -- [**S3**](https://docs.airbyte.io/integrations/destinations/s3) +- [**S3**](https://docs.airbyte.com/integrations/destinations/s3) 3 new sources: -- [**Harvest**](https://docs.airbyte.io/integrations/sources/harvest) -- [**Amplitude**](https://docs.airbyte.io/integrations/sources/amplitude) -- [**Posthog**](https://docs.airbyte.io/integrations/sources/posthog) +- [**Harvest**](https://docs.airbyte.com/integrations/sources/harvest) +- [**Amplitude**](https://docs.airbyte.com/integrations/sources/amplitude) +- [**Posthog**](https://docs.airbyte.com/integrations/sources/posthog) New features: @@ -498,8 +498,8 @@ Connector development updates: 2 new sources: -- [**Okta**](https://docs.airbyte.io/integrations/sources/okta) -- [**Amazon Seller Partner**](https://docs.airbyte.io/integrations/sources/amazon-seller-partner) +- [**Okta**](https://docs.airbyte.com/integrations/sources/okta) +- [**Amazon Seller Partner**](https://docs.airbyte.com/integrations/sources/amazon-seller-partner) New features: @@ -518,10 +518,10 @@ Bugfixes: 4 new sources: -- [**Asana**](https://docs.airbyte.io/integrations/sources/asana) -- [**Klaviyo**](https://docs.airbyte.io/integrations/sources/klaviyo) -- [**Recharge**](https://docs.airbyte.io/integrations/sources/recharge) -- [**Tempo**](https://docs.airbyte.io/integrations/sources/tempo) +- [**Asana**](https://docs.airbyte.com/integrations/sources/asana) +- [**Klaviyo**](https://docs.airbyte.com/integrations/sources/klaviyo) +- [**Recharge**](https://docs.airbyte.com/integrations/sources/recharge) +- [**Tempo**](https://docs.airbyte.com/integrations/sources/tempo) Progress on connectors: @@ -534,9 +534,9 @@ Progress on connectors: ## 05/18/2021 -1 new destination: [**MSSQL**](https://docs.airbyte.io/integrations/destinations/mssql) +1 new destination: [**MSSQL**](https://docs.airbyte.com/integrations/destinations/mssql) -1 new source: [**ClickHouse**](https://docs.airbyte.io/integrations/sources/clickhouse) +1 new source: [**ClickHouse**](https://docs.airbyte.com/integrations/sources/clickhouse) Progress on connectors: @@ -546,12 +546,12 @@ Progress on connectors: ## 05/11/2021 -1 new destination: [**MySQL**](https://docs.airbyte.io/integrations/destinations/mysql) +1 new destination: [**MySQL**](https://docs.airbyte.com/integrations/destinations/mysql) 2 new sources: -- [**Google Search Console**](https://docs.airbyte.io/integrations/sources/google-search-console) -- [**PokeAPI**](https://docs.airbyte.io/integrations/sources/pokeapi) \(talking about long tail and having fun ;\)\) +- [**Google Search Console**](https://docs.airbyte.com/integrations/sources/google-search-console) +- [**PokeAPI**](https://docs.airbyte.com/integrations/sources/pokeapi) \(talking about long tail and having fun ;\)\) Progress on connectors: @@ -563,8 +563,8 @@ Progress on connectors: 2 new sources: -- [**Smartsheets**](https://docs.airbyte.io/integrations/sources/smartsheets), thanks to [Nathan Nowack](https://github.com/zzstoatzz) -- [**Zendesk Chat**](https://docs.airbyte.io/integrations/sources/zendesk-chat) +- [**Smartsheets**](https://docs.airbyte.com/integrations/sources/smartsheets), thanks to [Nathan Nowack](https://github.com/zzstoatzz) +- [**Zendesk Chat**](https://docs.airbyte.com/integrations/sources/zendesk-chat) Progress on connectors: @@ -587,9 +587,9 @@ Progress on connectors: 3 new source connectors! -- [**Zendesk Talk**](https://docs.airbyte.io/integrations/sources/zendesk-talk) -- [**Iterable**](https://docs.airbyte.io/integrations/sources/iterable) -- [**QuickBooks**](https://docs.airbyte.io/integrations/sources/quickbooks-singer) +- [**Zendesk Talk**](https://docs.airbyte.com/integrations/sources/zendesk-talk) +- [**Iterable**](https://docs.airbyte.com/integrations/sources/iterable) +- [**QuickBooks**](https://docs.airbyte.com/integrations/sources/quickbooks-singer) Other progress on connectors: @@ -603,11 +603,11 @@ Other progress on connectors: ## 04/13/2021 -- New connector: [**Oracle DB**](https://docs.airbyte.io/integrations/sources/oracle), thanks to [Marcos Marx](https://github.com/marcosmarxm) +- New connector: [**Oracle DB**](https://docs.airbyte.com/integrations/sources/oracle), thanks to [Marcos Marx](https://github.com/marcosmarxm) ## 04/07/2021 -- New connector: [**Google Workspace Admin Reports**](https://docs.airbyte.io/integrations/sources/google-workspace-admin-reports) \(audit logs\) +- New connector: [**Google Workspace Admin Reports**](https://docs.airbyte.com/integrations/sources/google-workspace-admin-reports) \(audit logs\) - Bugfix in the base python connector library that caused errors to be silently skipped rather than failing the sync - **Exchangeratesapi.io** bugfix: to point to the updated API URL - **Redshift destination** bugfix: quote keywords “DATETIME” and “TIME” when used as identifiers @@ -624,12 +624,12 @@ Other progress on connectors: ## 03/22/2021 -- 2 new source connectors: [**Gitlab**](https://docs.airbyte.io/integrations/sources/gitlab) and [**Airbyte-native HubSpot**](https://docs.airbyte.io/integrations/sources/hubspot) -- Developing connectors now requires almost no interaction with Gradle, Airbyte’s monorepo build tool. If you’re building a Python connector, you never have to worry about developing outside your typical flow. See [the updated documentation](https://docs.airbyte.io/connector-development). +- 2 new source connectors: [**Gitlab**](https://docs.airbyte.com/integrations/sources/gitlab) and [**Airbyte-native HubSpot**](https://docs.airbyte.com/integrations/sources/hubspot) +- Developing connectors now requires almost no interaction with Gradle, Airbyte’s monorepo build tool. If you’re building a Python connector, you never have to worry about developing outside your typical flow. See [the updated documentation](https://docs.airbyte.com/connector-development). ## 03/15/2021 -- 2 new source connectors: [**Instagram**](https://docs.airbyte.io/integrations/sources/instagram) and [**Google Directory**](https://docs.airbyte.io/integrations/sources/google-directory) +- 2 new source connectors: [**Instagram**](https://docs.airbyte.com/integrations/sources/instagram) and [**Google Directory**](https://docs.airbyte.com/integrations/sources/google-directory) - **Facebook Marketing**: support of API v10 - **Google Analytics**: support incremental sync - **Jira**: bug fix to consistently pull all tickets @@ -657,8 +657,8 @@ Other progress on connectors: ## 02/15/2021 -- 1 new destination connector: [MeiliSearch](https://docs.airbyte.io/integrations/destinations/meilisearch) -- 2 new sources that support incremental append: [Freshdesk](https://docs.airbyte.io/integrations/sources/freshdesk) and [Sendgrid](https://docs.airbyte.io/integrations/sources/sendgrid) +- 1 new destination connector: [MeiliSearch](https://docs.airbyte.com/integrations/destinations/meilisearch) +- 2 new sources that support incremental append: [Freshdesk](https://docs.airbyte.com/integrations/sources/freshdesk) and [Sendgrid](https://docs.airbyte.com/integrations/sources/sendgrid) - Other fixes: - Thanks to [@ns-admetrics](https://github.com/ns-admetrics) for contributing an upgrade to the **Shopify** source connector which now provides the landing_site field containing UTM parameters in the Orders table. - **Sendgrid** source connector supports most available endpoints available in the API @@ -673,11 +673,11 @@ Other progress on connectors: ## 02/02/2021 - Sources that we improved reliability for \(and that became “certified”\): - - [Certified sources](https://docs.airbyte.io/integrations): Files and Shopify + - [Certified sources](https://docs.airbyte.com/integrations): Files and Shopify - Enhanced continuous testing for Tempo and Looker sources - Other fixes / features: - Correctly handle boolean types in the File Source - - Add docs for [App Store](https://docs.airbyte.io/integrations/sources/appstore) source + - Add docs for [App Store](https://docs.airbyte.com/integrations/sources/appstore) source - Fix a bug in Snowflake destination where the connector didn’t check for all needed write permissions, causing some syncs to fail ## 01/26/2021 diff --git a/docs/archive/changelog/platform.md b/docs/archive/changelog/platform.md index d27e9246e338..0da305f5822e 100644 --- a/docs/archive/changelog/platform.md +++ b/docs/archive/changelog/platform.md @@ -331,7 +331,7 @@ This interim patch period mostly contained stability changes for Airbyte Cloud, * Normalization now supports union data types * Support longform text inputs in the UI for cases where you need to preserve formatting on connector inputs like .pem keys * Expose the latest available connector versions in the API -* Airflow: published a new [tutorial](https://docs.airbyte.io/tutorials/using-the-airflow-airbyte-operator) for how to use the Airbyte operator. Thanks [@Marcos Marx](https://github.com/marcosmarxm) for writing the tutorial! +* Airflow: published a new [tutorial](https://docs.airbyte.com/tutorials/using-the-airflow-airbyte-operator) for how to use the Airbyte operator. Thanks [@Marcos Marx](https://github.com/marcosmarxm) for writing the tutorial! * Connector Contributions: All connectors now describe how to contribute to them without having to touch Airbyte’s monorepo build system -- just work on the connector in your favorite dev setup! ## [03-08-2021 - 0.17](https://github.com/airbytehq/airbyte/releases/tag/v0.17.0-alpha) @@ -422,7 +422,7 @@ This interim patch period mostly contained stability changes for Airbyte Cloud, ## [0.10.0](https://github.com/airbytehq/airbyte/milestone/12?closed=1) - delivered on 01/04/2021 -* You can now **deploy Airbyte on** [**Kuberbetes**](https://docs.airbyte.io/deploying-airbyte/on-kubernetes) _\*\*_\(alpha version\) +* You can now **deploy Airbyte on** [**Kuberbetes**](https://docs.airbyte.com/deploying-airbyte/on-kubernetes) _\*\*_\(alpha version\) * **Support incremental sync** for Mixpanel and HubSpot sources * **Fixes on connectors:** * Fixed a bug in the GitHub connector where the connector didn’t verify the provided API token was granted the correct permissions diff --git a/docs/archive/examples/build-a-slack-activity-dashboard.md b/docs/archive/examples/build-a-slack-activity-dashboard.md index f1a1969c7299..b63a2b65babb 100644 --- a/docs/archive/examples/build-a-slack-activity-dashboard.md +++ b/docs/archive/examples/build-a-slack-activity-dashboard.md @@ -6,7 +6,7 @@ description: Using Airbyte and Apache Superset ![](../../.gitbook/assets/46.png) -This article will show how to use [Airbyte](http://airbyte.io) - an open-source data integration platform - and [Apache Superset](https://superset.apache.org/) - an open-source data exploration platform - in order to build a Slack activity dashboard showing: +This article will show how to use [Airbyte](http://airbyte.com) - an open-source data integration platform - and [Apache Superset](https://superset.apache.org/) - an open-source data exploration platform - in order to build a Slack activity dashboard showing: * Total number of members of a Slack workspace * The evolution of the number of Slack workspace members @@ -26,7 +26,7 @@ Got it? Now let’s get started. ### a. Deploying Airbyte -There are several easy ways to deploy Airbyte, as listed [here](https://docs.airbyte.io/). For this tutorial, I will just use the [Docker Compose method](https://docs.airbyte.io/deploying-airbyte/local-deployment) from my workstation: +There are several easy ways to deploy Airbyte, as listed [here](https://docs.airbyte.com/). For this tutorial, I will just use the [Docker Compose method](https://docs.airbyte.com/deploying-airbyte/local-deployment) from my workstation: ```text # In your workstation terminal diff --git a/docs/archive/examples/slack-history.md b/docs/archive/examples/slack-history.md index ca78ec035533..6305798bffee 100644 --- a/docs/archive/examples/slack-history.md +++ b/docs/archive/examples/slack-history.md @@ -53,7 +53,7 @@ Once you see an Airbyte banner, the UI is ready to go at [http://localhost:8000/ ### b. Set Up Airbyte’s Slack Source Connector -In the Airbyte UI, select Slack from the dropdown. We provide step-by-step instructions for setting up the Slack source in Airbyte [here](https://docs.airbyte.io/integrations/sources/slack#setup-guide). These will walk you through how to complete the form on this page. +In the Airbyte UI, select Slack from the dropdown. We provide step-by-step instructions for setting up the Slack source in Airbyte [here](https://docs.airbyte.com/integrations/sources/slack#setup-guide). These will walk you through how to complete the form on this page. ![](../../.gitbook/assets/slack-history-setup-wizard.png) diff --git a/docs/archive/examples/zoom-activity-dashboard.md b/docs/archive/examples/zoom-activity-dashboard.md index 379931d8f33a..8dc8b2c98ad1 100644 --- a/docs/archive/examples/zoom-activity-dashboard.md +++ b/docs/archive/examples/zoom-activity-dashboard.md @@ -4,7 +4,7 @@ description: Using Airbyte and Tableau # Visualizing the Time Spent by Your Team in Zoom Calls -In this article, we will show you how you can understand how much your team leverages Zoom, or spends time in meetings, in a couple of minutes. We will be using [Airbyte](https://airbyte.io) \(an open-source data integration platform\) and [Tableau](https://www.tableau.com) \(a business intelligence and analytics software\) for this tutorial. +In this article, we will show you how you can understand how much your team leverages Zoom, or spends time in meetings, in a couple of minutes. We will be using [Airbyte](https://airbyte.com) \(an open-source data integration platform\) and [Tableau](https://www.tableau.com) \(a business intelligence and analytics software\) for this tutorial. Here is what we will cover: @@ -28,7 +28,7 @@ Let’s get started by replicating Zoom data using Airbyte. ### Launching Airbyte -In order to replicate Zoom data, we will need to use [Airbyte’s Zoom connector](https://docs.airbyte.io/integrations/sources/zoom). To do this, you need to start off Airbyte’s web app by opening up your terminal and navigating to Airbyte and running: +In order to replicate Zoom data, we will need to use [Airbyte’s Zoom connector](https://docs.airbyte.com/integrations/sources/zoom). To do this, you need to start off Airbyte’s web app by opening up your terminal and navigating to Airbyte and running: `docker-compose up` diff --git a/docs/archive/faq/differences-with/fivetran-vs-airbyte.md b/docs/archive/faq/differences-with/fivetran-vs-airbyte.md index d6f015218e9e..9a9fe1045660 100644 --- a/docs/archive/faq/differences-with/fivetran-vs-airbyte.md +++ b/docs/archive/faq/differences-with/fivetran-vs-airbyte.md @@ -1,8 +1,8 @@ # Fivetran vs Airbyte -We wrote an article, “[Open-source vs. Commercial Software: How to Solve the Data Integration Problem](https://airbyte.io/articles/data-engineering-thoughts/open-source-vs-commercial-software-how-to-better-solve-data-integration/),” in which we describe the pros and cons of Fivetran’s commercial approach and Airbyte’s open-source approach. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: +We wrote an article, “[Open-source vs. Commercial Software: How to Solve the Data Integration Problem](https://airbyte.com/articles/data-engineering-thoughts/open-source-vs-commercial-software-how-to-better-solve-data-integration/),” in which we describe the pros and cons of Fivetran’s commercial approach and Airbyte’s open-source approach. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: -![](https://airbyte.io/wp-content/uploads/2021/01/Airbyte-vs-Fivetran.png) +![](https://airbyte.com/wp-content/uploads/2021/01/Airbyte-vs-Fivetran.png) ## **Fivetran:** diff --git a/docs/archive/faq/differences-with/meltano-vs-airbyte.md b/docs/archive/faq/differences-with/meltano-vs-airbyte.md index 0b4aef9033b9..f8e2ff5fba64 100644 --- a/docs/archive/faq/differences-with/meltano-vs-airbyte.md +++ b/docs/archive/faq/differences-with/meltano-vs-airbyte.md @@ -1,10 +1,10 @@ # Meltano vs Airbyte -We wrote an article, “[The State of Open-Source Data Integration and ETL](https://airbyte.io/articles/data-engineering-thoughts/the-state-of-open-source-data-integration-and-etl/),” in which we list and compare all ETL-related open-source projects, including Meltano and Airbyte. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: +We wrote an article, “[The State of Open-Source Data Integration and ETL](https://airbyte.com/articles/data-engineering-thoughts/the-state-of-open-source-data-integration-and-etl/),” in which we list and compare all ETL-related open-source projects, including Meltano and Airbyte. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: ## **Meltano:** -* **Meltano is built on top of the Singer protocol, whereas Airbyte is built on top of the Airbyte protocol**. Having initially created Airbyte on top of Singer, we wrote about why we didn't move forward with it [here](https://airbyte.io/blog/why-you-should-not-build-your-data-pipeline-on-top-of-singer) and [here](https://airbyte.io/blog/airbyte-vs-singer-why-airbyte-is-not-built-on-top-of-singer). Summarized, the reasons were: Singer connectors didn't always adhere to the Singer protocol, had poor standardization and visibility in terms of quality, and community governance and support was abandoned by Stitch. By contrast, we aim to make Airbyte a product that ["just works"](https://airbyte.io/blog/our-truth-for-2021-airbyte-just-works) and always plan to maximize engagement within the Airbyte community. +* **Meltano is built on top of the Singer protocol, whereas Airbyte is built on top of the Airbyte protocol**. Having initially created Airbyte on top of Singer, we wrote about why we didn't move forward with it [here](https://airbyte.com/blog/why-you-should-not-build-your-data-pipeline-on-top-of-singer) and [here](https://airbyte.com/blog/airbyte-vs-singer-why-airbyte-is-not-built-on-top-of-singer). Summarized, the reasons were: Singer connectors didn't always adhere to the Singer protocol, had poor standardization and visibility in terms of quality, and community governance and support was abandoned by Stitch. By contrast, we aim to make Airbyte a product that ["just works"](https://airbyte.com/blog/our-truth-for-2021-airbyte-just-works) and always plan to maximize engagement within the Airbyte community. * **CLI-first approach:** Meltano was primarily built with a command line interface in mind. In that sense, they seem to target engineers with a preference for that interface. * **Integration with Airflow for orchestration:** You can either use Meltano alone for orchestration or with Airflow; Meltano works both ways. * All connectors must use Python. @@ -12,7 +12,7 @@ We wrote an article, “[The State of Open-Source Data Integration and ETL](http ## **Airbyte:** -In contrast, Airbyte is a company fully committed to the open-source project and has a [business model](https://handbook.airbyte.io/strategy/business-model) in mind around this project. Our [team](https://airbyte.io/about-us) are data integration experts that have built more than 1,000 integrations collectively at large scale. The team now counts 20 engineers working full-time on Airbyte. +In contrast, Airbyte is a company fully committed to the open-source project and has a [business model](https://handbook.airbyte.io/strategy/business-model) in mind around this project. Our [team](https://airbyte.com/about-us) are data integration experts that have built more than 1,000 integrations collectively at large scale. The team now counts 20 engineers working full-time on Airbyte. * **Airbyte supports more than 100 connectors after only 1 year since its inception**, 20% of which were built by the community. Our ambition is to support **200+ connectors by the end of 2021.** * Airbyte’s connectors are **usable out of the box through a UI and API,** with monitoring, scheduling and orchestration. Airbyte was built on the premise that a user, whatever their background, should be able to move data in 2 minutes. Data engineers might want to use raw data and their own transformation processes, or to use Airbyte’s API to include data integration in their workflows. On the other hand, analysts and data scientists might want to use normalized consolidated data in their database or data warehouses. Airbyte supports all these use cases. diff --git a/docs/archive/faq/differences-with/singer-vs-airbyte.md b/docs/archive/faq/differences-with/singer-vs-airbyte.md index 42342dcaed92..58edd43eedb0 100644 --- a/docs/archive/faq/differences-with/singer-vs-airbyte.md +++ b/docs/archive/faq/differences-with/singer-vs-airbyte.md @@ -2,10 +2,10 @@ If you want to understand the difference between Airbyte and Singer, you might be interested in 2 articles we wrote: -* “[Airbyte vs. Singer: Why Airbyte is not built on top of Singer](https://airbyte.io/articles/data-engineering-thoughts/airbyte-vs-singer-why-airbyte-is-not-built-on-top-of-singer/).” -* “[The State of Open-Source Data Integration and ETL](https://airbyte.io/articles/data-engineering-thoughts/the-state-of-open-source-data-integration-and-etl/),” in which we list and compare all ETL-related open-source projects, including Singer and Airbyte. As a summary, here are the differences: +* “[Airbyte vs. Singer: Why Airbyte is not built on top of Singer](https://airbyte.com/articles/data-engineering-thoughts/airbyte-vs-singer-why-airbyte-is-not-built-on-top-of-singer/).” +* “[The State of Open-Source Data Integration and ETL](https://airbyte.com/articles/data-engineering-thoughts/the-state-of-open-source-data-integration-and-etl/),” in which we list and compare all ETL-related open-source projects, including Singer and Airbyte. As a summary, here are the differences: -![](https://airbyte.io/wp-content/uploads/2020/10/Landscape-of-open-source-data-integration-platforms-4.png) +![](https://airbyte.com/wp-content/uploads/2020/10/Landscape-of-open-source-data-integration-platforms-4.png) ## **Singer:** diff --git a/docs/archive/faq/differences-with/stitchdata-vs-airbyte.md b/docs/archive/faq/differences-with/stitchdata-vs-airbyte.md index f5ea358f5851..ec612ea9b2b1 100644 --- a/docs/archive/faq/differences-with/stitchdata-vs-airbyte.md +++ b/docs/archive/faq/differences-with/stitchdata-vs-airbyte.md @@ -1,8 +1,8 @@ # StitchData vs Airbyte -We wrote an article, “[Open-source vs. Commercial Software: How to Solve the Data Integration Problem](https://airbyte.io/articles/data-engineering-thoughts/open-source-vs-commercial-software-how-to-better-solve-data-integration/),” in which we describe the pros and cons of StitchData’s commercial approach and Airbyte’s open-source approach. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: +We wrote an article, “[Open-source vs. Commercial Software: How to Solve the Data Integration Problem](https://airbyte.com/articles/data-engineering-thoughts/open-source-vs-commercial-software-how-to-better-solve-data-integration/),” in which we describe the pros and cons of StitchData’s commercial approach and Airbyte’s open-source approach. Don’t hesitate to check it out for more detailed arguments. As a summary, here are the differences: -![](https://airbyte.io/wp-content/uploads/2020/10/Open-source-vs-commercial-approach-2048x1843.png) +![](https://airbyte.com/wp-content/uploads/2020/10/Open-source-vs-commercial-approach-2048x1843.png) ## StitchData: diff --git a/docs/cloud/core-concepts.md b/docs/cloud/core-concepts.md index e362c31cd2b6..1439c769e013 100644 --- a/docs/cloud/core-concepts.md +++ b/docs/cloud/core-concepts.md @@ -158,7 +158,7 @@ Normalizing data may cause an increase in your destination's compute cost. This A workspace is a grouping of sources, destinations, connections, and other configurations. It lets you collaborate with team members and share resources across your team under a shared billing account. -When you [sign up](http://cloud.airbyte.io/signup) for Airbyte Cloud, we automatically create your first workspace where you are the only user with access. You can set up your sources and destinations to start syncing data and invite other users to join your workspace. +When you [sign up](http://cloud.airbyte.com/signup) for Airbyte Cloud, we automatically create your first workspace where you are the only user with access. You can set up your sources and destinations to start syncing data and invite other users to join your workspace. ## Glossary of Terms diff --git a/docs/cloud/getting-started-with-airbyte-cloud.md b/docs/cloud/getting-started-with-airbyte-cloud.md index 5a2c6a461063..d8c90e45de3e 100644 --- a/docs/cloud/getting-started-with-airbyte-cloud.md +++ b/docs/cloud/getting-started-with-airbyte-cloud.md @@ -6,7 +6,7 @@ This page guides you through setting up your Airbyte Cloud account, setting up a To use Airbyte Cloud: -1. If you haven't already, [sign up for Airbyte Cloud](https://cloud.airbyte.io/signup?utm_campaign=22Q1_AirbyteCloudSignUpCampaign_Trial&utm_source=Docs&utm_content=SetupGuide) using your email address, Google login, or GitHub login. +1. If you haven't already, [sign up for Airbyte Cloud](https://cloud.airbyte.com/signup?utm_campaign=22Q1_AirbyteCloudSignUpCampaign_Trial&utm_source=Docs&utm_content=SetupGuide) using your email address, Google login, or GitHub login. Airbyte Cloud offers a 14-day free trial. For more information, see [Pricing](https://airbyte.com/pricing). diff --git a/docs/cloud/managing-airbyte-cloud.md b/docs/cloud/managing-airbyte-cloud.md index fc62264ee880..a09c7341eaaa 100644 --- a/docs/cloud/managing-airbyte-cloud.md +++ b/docs/cloud/managing-airbyte-cloud.md @@ -14,7 +14,7 @@ Airbyte [credits](https://airbyte.com/pricing) are assigned per workspace and ca To add a user to your workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Access Management**. @@ -32,7 +32,7 @@ To add a user to your workspace: To remove a user from your workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Access Management**. @@ -44,7 +44,7 @@ To remove a user from your workspace: To rename a workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **General Settings**. @@ -56,7 +56,7 @@ To rename a workspace: To delete a workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **General Settings**. @@ -82,7 +82,7 @@ You can use one or multiple workspaces with Airbyte Cloud. To switch between workspaces: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click the current workspace name under the Airbyte logo in the navigation bar. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click the current workspace name under the Airbyte logo in the navigation bar. 2. Click **View all workspaces**. @@ -108,7 +108,7 @@ While the data is processed in a data plane in the chosen residency, the cursor To choose your default data residency: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Data Residency**. @@ -126,7 +126,7 @@ Depending on your network configuration, you may need to add [IP addresses](http To set up Slack notifications: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Notifications**. @@ -156,7 +156,7 @@ Understanding the following limitations will help you better manage Airbyte Clou The sync summary displays information about the data moved during a sync. To view the sync summary: -1. On the [Airbyte Cloud](http://cloud.airbyte.io/) dashboard, click **Connections**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com/) dashboard, click **Connections**. 2. Click a connection in the list to view its sync history. @@ -187,7 +187,7 @@ In a successful sync, the number of emitted records and committed records should ## Edit stream configuration -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection you want to change. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection you want to change. 2. Click the **Replication** tab. @@ -352,7 +352,7 @@ To get notified when your source schema changes: Connection state provides additional information about incremental syncs. It includes the most recent values for the global or stream-level cursors, which can aid in debugging or determining which data will be included in the next syncs. To display the connection state: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection you want to display. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection you want to display. 2. Click the **Settings** tab on the Connection page. @@ -365,7 +365,7 @@ You can choose the data residency for your connection in the connection settings To choose the data residency for your connection: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection that you want to change. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection that you want to change. 2. Click the **Settings** tab. diff --git a/docs/cloud/managing-airbyte-cloud/edit-stream-configuration.md b/docs/cloud/managing-airbyte-cloud/edit-stream-configuration.md index 87545bfd368f..950bfb303e83 100644 --- a/docs/cloud/managing-airbyte-cloud/edit-stream-configuration.md +++ b/docs/cloud/managing-airbyte-cloud/edit-stream-configuration.md @@ -2,7 +2,7 @@ By editing stream configurations, you can customize how your data syncs to the destination. This allows you to manage aspects of the sync, such as replication frequency, destination namespace, and ensuring your data is written to the correct location. -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection you want to change. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection you want to change. 2. Click the **Replication** tab. diff --git a/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications.md b/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications.md index 82975cf9b0d0..849f67de2737 100644 --- a/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications.md +++ b/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications.md @@ -6,7 +6,7 @@ This page provides guidance on how to manage notifications for Airbyte Cloud, al To set up Webhook notifications: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Notifications**. diff --git a/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-workspace.md b/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-workspace.md index 6d6dc563357b..19d299da833c 100644 --- a/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-workspace.md +++ b/docs/cloud/managing-airbyte-cloud/manage-airbyte-cloud-workspace.md @@ -10,7 +10,7 @@ Airbyte [credits](https://airbyte.com/pricing) are assigned per workspace and ca To add a user to your workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Access Management**. @@ -28,7 +28,7 @@ To add a user to your workspace: To remove a user from your workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Access Management**. @@ -40,7 +40,7 @@ To remove a user from your workspace: To rename a workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **General Settings**. @@ -52,7 +52,7 @@ To rename a workspace: To delete a workspace: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **General Settings**. @@ -78,7 +78,7 @@ You can use one or multiple workspaces with Airbyte Cloud, which gives you flexi To switch between workspaces: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click the current workspace name under the Airbyte logo in the navigation bar. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click the current workspace name under the Airbyte logo in the navigation bar. 2. Click **View all workspaces**. diff --git a/docs/cloud/managing-airbyte-cloud/manage-data-residency.md b/docs/cloud/managing-airbyte-cloud/manage-data-residency.md index 4b928a58fb60..cfb539fbfc72 100644 --- a/docs/cloud/managing-airbyte-cloud/manage-data-residency.md +++ b/docs/cloud/managing-airbyte-cloud/manage-data-residency.md @@ -22,7 +22,7 @@ While the data is processed in a data plane in the chosen residency, the cursor To choose your default data residency: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Settings**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Settings**. 2. Click **Data Residency**. @@ -41,7 +41,7 @@ You can choose the data residency for your connection in the connection settings To choose the data residency for your connection: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection that you want to change. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection that you want to change. 2. Click the **Settings** tab. diff --git a/docs/cloud/managing-airbyte-cloud/review-connection-state.md b/docs/cloud/managing-airbyte-cloud/review-connection-state.md index 19dacacc5ae0..e2596f39ec2e 100644 --- a/docs/cloud/managing-airbyte-cloud/review-connection-state.md +++ b/docs/cloud/managing-airbyte-cloud/review-connection-state.md @@ -3,7 +3,7 @@ The connection state provides additional information about incremental syncs. It includes the most recent values for the global or stream-level cursors, which can aid in debugging or determining which data will be included in the next sync. To review the connection state: -1. On the [Airbyte Cloud](http://cloud.airbyte.io) dashboard, click **Connections** and then click the connection you want to display. +1. On the [Airbyte Cloud](http://cloud.airbyte.com) dashboard, click **Connections** and then click the connection you want to display. 2. Click the **Settings** tab on the Connection page. diff --git a/docs/cloud/managing-airbyte-cloud/review-sync-summary.md b/docs/cloud/managing-airbyte-cloud/review-sync-summary.md index 1af06db03df6..eebab7fc47b0 100644 --- a/docs/cloud/managing-airbyte-cloud/review-sync-summary.md +++ b/docs/cloud/managing-airbyte-cloud/review-sync-summary.md @@ -2,7 +2,7 @@ The sync summary displays information about synced data, such as the amount of data moved, the number of records read and committed, and the total sync time. Reviewing this summary can help you monitor the sync performance and identify any potential issues. To review the sync summary: -1. On the [Airbyte Cloud](http://cloud.airbyte.io/) dashboard, click **Connections**. +1. On the [Airbyte Cloud](http://cloud.airbyte.com/) dashboard, click **Connections**. 2. Click a connection in the list to view its sync history. diff --git a/docs/connector-development/cdk-python/incremental-stream.md b/docs/connector-development/cdk-python/incremental-stream.md index b9db5260e0c9..82f5a0b2fc1c 100644 --- a/docs/connector-development/cdk-python/incremental-stream.md +++ b/docs/connector-development/cdk-python/incremental-stream.md @@ -13,7 +13,7 @@ Several new pieces are essential to understand how incrementality works with the ### `AirbyteStateMessage` -The `AirbyteStateMessage` persists state between syncs, and allows a new sync to pick up from where the previous sync last finished. See the [incremental sync guide](https://docs.airbyte.io/understanding-airbyte/connections/incremental-append) for more information. +The `AirbyteStateMessage` persists state between syncs, and allows a new sync to pick up from where the previous sync last finished. See the [incremental sync guide](https://docs.airbyte.com/understanding-airbyte/connections/incremental-append) for more information. ### Cursor fields diff --git a/docs/connector-development/config-based/tutorial/3-connecting-to-the-API-source.md b/docs/connector-development/config-based/tutorial/3-connecting-to-the-API-source.md index ffcefaaf4c53..0afbd220633f 100644 --- a/docs/connector-development/config-based/tutorial/3-connecting-to-the-API-source.md +++ b/docs/connector-development/config-based/tutorial/3-connecting-to-the-API-source.md @@ -22,7 +22,7 @@ Let's populate the specification (`spec`) and the configuration (`secrets/config ```yaml spec: - documentation_url: https://docs.airbyte.io/integrations/sources/exchangeratesapi + documentation_url: https://docs.airbyte.com/integrations/sources/exchangeratesapi connection_specification: $schema: http://json-schema.org/draft-07/schema# title: exchangeratesapi.io Source Spec @@ -170,7 +170,7 @@ check: stream_names: - "rates" spec: - documentation_url: https://docs.airbyte.io/integrations/sources/exchangeratesapi + documentation_url: https://docs.airbyte.com/integrations/sources/exchangeratesapi connection_specification: $schema: http://json-schema.org/draft-07/schema# title: exchangeratesapi.io Source Spec @@ -221,4 +221,4 @@ Next, we'll [extract the records from the response](4-reading-data.md) - [Request options providers](../understanding-the-yaml-file/request-options.md) - [Schema definition](../../cdk-python/schemas.md) - [Connector specification reference](../../connector-specification-reference.md) -- [Beginner's guide to catalog](../../../understanding-airbyte/beginners-guide-to-catalog.md) \ No newline at end of file +- [Beginner's guide to catalog](../../../understanding-airbyte/beginners-guide-to-catalog.md) diff --git a/docs/connector-development/config-based/tutorial/4-reading-data.md b/docs/connector-development/config-based/tutorial/4-reading-data.md index bcbce8a78669..e2717be88d75 100644 --- a/docs/connector-development/config-based/tutorial/4-reading-data.md +++ b/docs/connector-development/config-based/tutorial/4-reading-data.md @@ -22,7 +22,7 @@ Let's first add the stream to the configured catalog in `source-exchange-rates-t ``` The configured catalog declares the sync modes supported by the stream (full refresh or incremental). -See the [catalog guide](https://docs.airbyte.io/understanding-airbyte/beginners-guide-to-catalog) for more information. +See the [catalog guide](https://docs.airbyte.com/understanding-airbyte/beginners-guide-to-catalog) for more information. Let's define the stream schema in `source-exchange-rates-tutorial/source_exchange_rates_tutorial/schemas/rates.json` @@ -69,4 +69,4 @@ Next, we'll [enhance the connector to read data for a given date, which will ena ## More readings - [Record selector](../understanding-the-yaml-file/record-selector.md) -- [Catalog guide](https://docs.airbyte.io/understanding-airbyte/beginners-guide-to-catalog) +- [Catalog guide](https://docs.airbyte.com/understanding-airbyte/beginners-guide-to-catalog) diff --git a/docs/connector-development/config-based/tutorial/5-incremental-reads.md b/docs/connector-development/config-based/tutorial/5-incremental-reads.md index 53329679cc10..51d1e24bc326 100644 --- a/docs/connector-development/config-based/tutorial/5-incremental-reads.md +++ b/docs/connector-development/config-based/tutorial/5-incremental-reads.md @@ -11,7 +11,7 @@ First we'll update the spec block in `source_exchange_rates_tutorial/manifest.ya ```yaml spec: - documentation_url: https://docs.airbyte.io/integrations/sources/exchangeratesapi + documentation_url: https://docs.airbyte.com/integrations/sources/exchangeratesapi connection_specification: $schema: http://json-schema.org/draft-07/schema# title: exchangeratesapi.io Source Spec @@ -203,7 +203,7 @@ check: stream_names: - "rates" spec: - documentation_url: https://docs.airbyte.io/integrations/sources/exchangeratesapi + documentation_url: https://docs.airbyte.com/integrations/sources/exchangeratesapi connection_specification: $schema: http://json-schema.org/draft-07/schema# title: exchangeratesapi.io Source Spec diff --git a/docs/connector-development/tutorials/adding-incremental-sync.md b/docs/connector-development/tutorials/adding-incremental-sync.md index 8603df62d21b..992c9d9ed4b5 100644 --- a/docs/connector-development/tutorials/adding-incremental-sync.md +++ b/docs/connector-development/tutorials/adding-incremental-sync.md @@ -213,7 +213,7 @@ To enable these tests, modify the existing `acceptance-test-config.yml` by addin Your full `acceptance-test-config.yml` should look something like this: ```yaml -# See [Connector Acceptance Tests](https://docs.airbyte.io/connector-development/testing-connectors/connector-acceptance-tests-reference) +# See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) # for more information about how to configure these tests connector_image: airbyte/source-stock-ticker-api:dev tests: diff --git a/docs/connector-development/tutorials/build-a-connector-the-hard-way.md b/docs/connector-development/tutorials/build-a-connector-the-hard-way.md index acd9bd61a27b..75fd0a0e6772 100644 --- a/docs/connector-development/tutorials/build-a-connector-the-hard-way.md +++ b/docs/connector-development/tutorials/build-a-connector-the-hard-way.md @@ -8,7 +8,7 @@ This tutorial walks you through building a simple Airbyte source without using a * [The Airbyte Specification](../../understanding-airbyte/airbyte-protocol.md) and the interface implemented by a source connector * [The AirbyteCatalog](../../understanding-airbyte/beginners-guide-to-catalog.md) -* [Packaging your connector](https://docs.airbyte.io/connector-development#1.-implement-and-package-the-connector) +* [Packaging your connector](https://docs.airbyte.com/connector-development#1.-implement-and-package-the-connector) * [Testing your connector](../testing-connectors/connector-acceptance-tests-reference.md) At the end of this tutorial, you will have a working source that you will be able to use in the Airbyte UI. @@ -147,7 +147,7 @@ Let's create a [JSONSchema](http://json-schema.org/) file `spec.json` encoding t } ``` -* `documentationUrl` is the URL that will appear in the UI for the user to gain more info about this connector. Typically this points to `docs.airbyte.io/integrations/sources/source-` but to keep things simple we won't show adding documentation +* `documentationUrl` is the URL that will appear in the UI for the user to gain more info about this connector. Typically this points to `docs.airbyte.com/integrations/sources/source-` but to keep things simple we won't show adding documentation * `title` is the "human readable" title displayed in the UI. Without this field, The Stock Ticker field will have the title `stock_ticker` in the UI * `description` will be shown in the Airbyte UI under each field to help the user understand it * `airbyte_secret` used by Airbyte to determine if the field should be displayed as a password \(e.g: `********`\) in the UI and not readable from the API @@ -986,7 +986,7 @@ The code generator should have already generated a YAML file which configures th ```yaml -# See [Connector Acceptance Tests](https://docs.airbyte.io/connector-development/testing-connectors/connector-acceptance-tests-reference) +# See [Connector Acceptance Tests](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference) # for more information about how to configure these tests connector_image: airbyte/source-stock-ticker-api:dev acceptance_tests: diff --git a/docs/connector-development/tutorials/building-a-java-destination.md b/docs/connector-development/tutorials/building-a-java-destination.md index 7644c4346e44..fb91b4f52c1f 100644 --- a/docs/connector-development/tutorials/building-a-java-destination.md +++ b/docs/connector-development/tutorials/building-a-java-destination.md @@ -185,7 +185,7 @@ docker run -v $(pwd)/secrets:/secrets --rm airbyte/destination-:dev check The `write` operation is the main workhorse of a destination connector: it reads input data from the source and writes it to the underlying destination. It takes as input the config file used to run the connector as well as the configured catalog: the file used to describe the schema of the incoming data and how it should be written to the destination. Its "output" is two things: 1. Data written to the underlying destination -2. `AirbyteMessage`s of type `AirbyteStateMessage`, written to stdout to indicate which records have been written so far during a sync. It's important to output these messages when possible in order to avoid re-extracting messages from the source. See the [write operation protocol reference](https://docs.airbyte.io/understanding-airbyte/airbyte-protocol#write) for more information. +2. `AirbyteMessage`s of type `AirbyteStateMessage`, written to stdout to indicate which records have been written so far during a sync. It's important to output these messages when possible in order to avoid re-extracting messages from the source. See the [write operation protocol reference](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol#write) for more information. To implement the `write` Airbyte operation, implement the `getConsumer` method in your generated `Destination.java` file. Here are some example implementations from different destination conectors: diff --git a/docs/connector-development/tutorials/building-a-python-destination.md b/docs/connector-development/tutorials/building-a-python-destination.md index ac7943ce9cb7..4e744e4835e0 100644 --- a/docs/connector-development/tutorials/building-a-python-destination.md +++ b/docs/connector-development/tutorials/building-a-python-destination.md @@ -135,7 +135,7 @@ Each destination contains a specification written in JsonSchema that describes t Some notes about fields in the output spec: -* `supportsNormalization` is a boolean which indicates if this connector supports [basic normalization via DBT](https://docs.airbyte.io/understanding-airbyte/basic-normalization). If true, `supportsDBT` must also be true. +* `supportsNormalization` is a boolean which indicates if this connector supports [basic normalization via DBT](https://docs.airbyte.com/understanding-airbyte/basic-normalization). If true, `supportsDBT` must also be true. * `supportsDBT` is a boolean which indicates whether this destination is compatible with DBT. If set to true, the user can define custom DBT transformations that run on this destination after each successful sync. This must be true if `supportsNormalization` is set to true. * `supported_destination_sync_modes`: An array of strings declaring the sync modes supported by this connector. The available options are: * `overwrite`: The connector can be configured to wipe any existing data in a stream before writing new data @@ -174,7 +174,7 @@ python main.py check --config secrets/config.json The `write` operation is the main workhorse of a destination connector: it reads input data from the source and writes it to the underlying destination. It takes as input the config file used to run the connector as well as the configured catalog: the file used to describe the schema of the incoming data and how it should be written to the destination. Its "output" is two things: 1. Data written to the underlying destination -2. `AirbyteMessage`s of type `AirbyteStateMessage`, written to stdout to indicate which records have been written so far during a sync. It's important to output these messages when possible in order to avoid re-extracting messages from the source. See the [write operation protocol reference](https://docs.airbyte.io/understanding-airbyte/airbyte-protocol#write) for more information. +2. `AirbyteMessage`s of type `AirbyteStateMessage`, written to stdout to indicate which records have been written so far during a sync. It's important to output these messages when possible in order to avoid re-extracting messages from the source. See the [write operation protocol reference](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol#write) for more information. To implement the `write` Airbyte operation, implement the `write` method in your generated `destination.py` file. [Here is an example implementation](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/destination-kvdb/destination_kvdb/destination.py) from the KvDB destination connector. diff --git a/docs/connector-development/tutorials/cdk-speedrun-deprecated.md b/docs/connector-development/tutorials/cdk-speedrun-deprecated.md index 36e6805484c5..be2be8f4c317 100644 --- a/docs/connector-development/tutorials/cdk-speedrun-deprecated.md +++ b/docs/connector-development/tutorials/cdk-speedrun-deprecated.md @@ -38,7 +38,7 @@ We're working with the Exchange Rates API, so we need to define our input schema ```javascript { - "documentationUrl": "https://docs.airbyte.io/integrations/sources/exchangeratesapi", + "documentationUrl": "https://docs.airbyte.com/integrations/sources/exchangeratesapi", "connectionSpecification": { "$schema": "http://json-schema.org/draft-07/schema#", "title": "Python Http Example Spec", diff --git a/docs/connector-development/tutorials/cdk-speedrun.md b/docs/connector-development/tutorials/cdk-speedrun.md index 0c1f19e8758b..6ce033267eb6 100644 --- a/docs/connector-development/tutorials/cdk-speedrun.md +++ b/docs/connector-development/tutorials/cdk-speedrun.md @@ -44,7 +44,7 @@ cd source_python_http_example We're working with the PokeAPI, so we need to define our input schema to reflect that. Open the `spec.yaml` file here and replace it with: ```yaml -documentationUrl: https://docs.airbyte.io/integrations/sources/pokeapi +documentationUrl: https://docs.airbyte.com/integrations/sources/pokeapi connectionSpecification: $schema: http://json-schema.org/draft-07/schema# title: Pokeapi Spec @@ -164,7 +164,7 @@ class Pokemon(HttpStream): Now download [this file](https://github.com/airbytehq/airbyte/blob/master/airbyte-cdk/python/docs/tutorials/http_api_source_assets/pokemon.json). Name it `pokemon.json` and place it in `/source_python_http_example/schemas`. -This file defines your output schema for every endpoint that you want to implement. Normally, this will likely be the most time-consuming section of the connector development process, as it requires defining the output of the endpoint exactly. This is really important, as Airbyte needs to have clear expectations for what the stream will output. Note that the name of this stream will be consistent in the naming of the JSON schema and the `HttpStream` class, as `pokemon.json` and `Pokemon` respectively in this case. Learn more about schema creation [here](https://docs.airbyte.io/connector-development/cdk-python/full-refresh-stream#defining-the-streams-schema). +This file defines your output schema for every endpoint that you want to implement. Normally, this will likely be the most time-consuming section of the connector development process, as it requires defining the output of the endpoint exactly. This is really important, as Airbyte needs to have clear expectations for what the stream will output. Note that the name of this stream will be consistent in the naming of the JSON schema and the `HttpStream` class, as `pokemon.json` and `Pokemon` respectively in this case. Learn more about schema creation [here](https://docs.airbyte.com/connector-development/cdk-python/full-refresh-stream#defining-the-streams-schema). Test your discover function. You should receive a fairly large JSON object in return. @@ -221,7 +221,7 @@ class Pokemon(HttpStream): return None ``` -We now need a catalog that defines all of our streams. We only have one stream: `Pokemon`. Download that file [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-cdk/python/docs/tutorials/http_api_source_assets/configured_catalog_pokeapi.json). Place it in `/sample_files` named as `configured_catalog.json`. More clearly, this is where we tell Airbyte all the streams/endpoints we support for the connector and in which sync modes Airbyte can run the connector on. Learn more about the AirbyteCatalog [here](https://docs.airbyte.io/understanding-airbyte/beginners-guide-to-catalog) and learn more about sync modes [here](https://docs.airbyte.io/understanding-airbyte/connections#sync-modes). +We now need a catalog that defines all of our streams. We only have one stream: `Pokemon`. Download that file [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-cdk/python/docs/tutorials/http_api_source_assets/configured_catalog_pokeapi.json). Place it in `/sample_files` named as `configured_catalog.json`. More clearly, this is where we tell Airbyte all the streams/endpoints we support for the connector and in which sync modes Airbyte can run the connector on. Learn more about the AirbyteCatalog [here](https://docs.airbyte.com/understanding-airbyte/beginners-guide-to-catalog) and learn more about sync modes [here](https://docs.airbyte.com/understanding-airbyte/connections#sync-modes). Let's read some data. diff --git a/docs/connector-development/tutorials/cdk-tutorial-python-http/declare-schema.md b/docs/connector-development/tutorials/cdk-tutorial-python-http/declare-schema.md index 78c3393343ea..591196a83295 100644 --- a/docs/connector-development/tutorials/cdk-tutorial-python-http/declare-schema.md +++ b/docs/connector-development/tutorials/cdk-tutorial-python-http/declare-schema.md @@ -1,6 +1,6 @@ # Step 5: Declare the Schema -The `discover` method of the Airbyte Protocol returns an `AirbyteCatalog`: an object which declares all the streams output by a connector and their schemas. It also declares the sync modes supported by the stream \(full refresh or incremental\). See the [catalog tutorial](https://docs.airbyte.io/understanding-airbyte/beginners-guide-to-catalog) for more information. +The `discover` method of the Airbyte Protocol returns an `AirbyteCatalog`: an object which declares all the streams output by a connector and their schemas. It also declares the sync modes supported by the stream \(full refresh or incremental\). See the [catalog tutorial](https://docs.airbyte.com/understanding-airbyte/beginners-guide-to-catalog) for more information. This is a simple task with the Airbyte CDK. For each stream in our connector we'll need to: diff --git a/docs/connector-development/tutorials/cdk-tutorial-python-http/define-inputs.md b/docs/connector-development/tutorials/cdk-tutorial-python-http/define-inputs.md index 53b98e8f379f..0cbe0bce93c9 100644 --- a/docs/connector-development/tutorials/cdk-tutorial-python-http/define-inputs.md +++ b/docs/connector-development/tutorials/cdk-tutorial-python-http/define-inputs.md @@ -4,14 +4,14 @@ Each connector declares the inputs it needs to read data from the underlying dat The simplest way to implement this is by creating a `spec.yaml` file in `source_/spec.yaml` which describes your connector's inputs according to the [ConnectorSpecification](https://github.com/airbytehq/airbyte/blob/master/docs/understanding-airbyte/airbyte-protocol.md#spec) schema. This is a good place to start when developing your source. Using JsonSchema, define what the inputs are \(e.g. username and password\). Here's [an example](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-stripe/source_stripe/spec.yaml) of what the `spec.yaml` looks like for the Stripe API source. -For more details on what the spec is, you can read about the Airbyte Protocol [here](https://docs.airbyte.io/understanding-airbyte/airbyte-protocol). +For more details on what the spec is, you can read about the Airbyte Protocol [here](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol). The generated code that Airbyte provides, handles implementing the `spec` method for you. It assumes that there will be a file called `spec.yaml` in the same directory as `source.py`. If you have declared the necessary JsonSchema in `spec.yaml` you should be done with this step. Given that we'll pulling currency data for our example source, we'll define the following `spec.yaml`: ```yaml -documentationUrl: https://docs.airbyte.io/integrations/sources/exchangeratesapi +documentationUrl: https://docs.airbyte.com/integrations/sources/exchangeratesapi connectionSpecification: $schema: http://json-schema.org/draft-07/schema# title: Python Http Tutorial Spec diff --git a/docs/connector-development/ux-handbook.md b/docs/connector-development/ux-handbook.md index dfe2f9f26fe3..5253df5e9ed6 100644 --- a/docs/connector-development/ux-handbook.md +++ b/docs/connector-development/ux-handbook.md @@ -239,7 +239,7 @@ In some cases, describing schemas is impossible to do reliably. For example, Mon That is, we would rather not describe a schema at all than describe it incorrectly, as incorrect descriptions **will** lead to failures downstream. -To keep schema descriptions reliable, [automate schema generation](https://docs.airbyte.io/connector-development/cdk-python/schemas#generating-schemas-from-openapi-definitions) whenever possible. +To keep schema descriptions reliable, [automate schema generation](https://docs.airbyte.com/connector-development/cdk-python/schemas#generating-schemas-from-openapi-definitions) whenever possible. #### Be very cautious about breaking changes to output schemas @@ -266,7 +266,7 @@ For example, to set up CDC for databases, a user must create logical replication ### External Documentation -This section is concerned with the external-facing documentation of a connector that goes in [https://docs.airbyte.io](https://docs.airbyte.io) e.g: [this one](https://docs.airbyte.io/integrations/sources/amazon-seller-partner) +This section is concerned with the external-facing documentation of a connector that goes in [https://docs.airbyte.com](https://docs.airbyte.com) e.g: [this one](https://docs.airbyte.com/integrations/sources/amazon-seller-partner) **Documentation should communicate persona-impacting behaviors** diff --git a/docs/contributing-to-airbyte/README.md b/docs/contributing-to-airbyte/README.md index 38cf606bc636..b59990de1041 100644 --- a/docs/contributing-to-airbyte/README.md +++ b/docs/contributing-to-airbyte/README.md @@ -85,7 +85,7 @@ The contributing guide for docs can be found [here](updating-documentation.md). ### **Community content** -We welcome contributions as new tutorials / showcases / articles, or to any of the existing guides on our [tutorials page](https://airbyte.io/tutorials): +We welcome contributions as new tutorials / showcases / articles, or to any of the existing guides on our [tutorials page](https://airbyte.com/tutorials): * Fix errors in existing tutorials * Add new tutorials \(please reach out to us if you have ideas to avoid duplicate work\) diff --git a/docs/deploying-airbyte/on-cloud.md b/docs/deploying-airbyte/on-cloud.md index 6d7fa52f9135..1771acc1188d 100644 --- a/docs/deploying-airbyte/on-cloud.md +++ b/docs/deploying-airbyte/on-cloud.md @@ -8,7 +8,7 @@ Airbyte Cloud requires no setup and can be immediately run from your web browser **1. Using the Airbyte Cloud invite link provided to you, click `Sign up`, and verify your email.** -If you don't have an invite, sign up [here!](https://airbyte.io/cloud-waitlist) +If you don't have an invite, sign up [here!](https://airbyte.com/cloud-waitlist) **2. Click on the default workspace.** diff --git a/docs/integrations/destinations/bigquery.md b/docs/integrations/destinations/bigquery.md index e19d1515c13c..999aeda36e30 100644 --- a/docs/integrations/destinations/bigquery.md +++ b/docs/integrations/destinations/bigquery.md @@ -44,7 +44,7 @@ You can use BigQuery's [`INSERT`](https://cloud.google.com/bigquery/docs/referen ### Step 2: Set up the BigQuery connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Destinations** and then click **+ New destination**. 3. On the Set up the destination page, select **BigQuery** or **BigQuery (denormalized typed struct)** from the **Destination type** dropdown depending on whether you want to set up the connector in [BigQuery](#connector-modes) or [BigQuery (Denormalized)](#connector-modes) mode. 4. Enter the name for the BigQuery connector. @@ -189,4 +189,4 @@ Now that you have set up the BigQuery destination connector, check out the follo | 0.3.10 | 2021-07-28 | [3549](https://github.com/airbytehq/airbyte/issues/3549) | Add extended logs and made JobId filled with region and projectId | | 0.3.9 | 2021-07-28 | [5026](https://github.com/airbytehq/airbyte/pull/5026) | Add sanitized json fields in raw tables to handle quotes in column names | | 0.3.6 | 2021-06-18 | [3947](https://github.com/airbytehq/airbyte/issues/3947) | Service account credentials are now optional. | -| 0.3.4 | 2021-06-07 | [3277](https://github.com/airbytehq/airbyte/issues/3277) | Add dataset location option | \ No newline at end of file +| 0.3.4 | 2021-06-07 | [3277](https://github.com/airbytehq/airbyte/issues/3277) | Add dataset location option | diff --git a/docs/integrations/destinations/chargify.md b/docs/integrations/destinations/chargify.md index 1d170e4d2750..f8c65fab7d00 100644 --- a/docs/integrations/destinations/chargify.md +++ b/docs/integrations/destinations/chargify.md @@ -7,7 +7,7 @@ description: >- ## Overview -The Airbyte Chargify destination allows you to stream data from any [Airbyte Source](https://airbyte.io/connectors?connector-type=Sources) into [Chargify](http://chargify.com) for [custom analysis](http://chargify.com/business-intelligence) and [multi-attribute, usage-based billing](http://chargify.com/events-based-billing). Chargify is the leading billing and subscription management software built for the evolving needs of fast-growth companies. +The Airbyte Chargify destination allows you to stream data from any [Airbyte Source](https://airbyte.com/connectors?connector-type=Sources) into [Chargify](http://chargify.com) for [custom analysis](http://chargify.com/business-intelligence) and [multi-attribute, usage-based billing](http://chargify.com/events-based-billing). Chargify is the leading billing and subscription management software built for the evolving needs of fast-growth companies. ### Sync overview diff --git a/docs/integrations/destinations/databricks.md b/docs/integrations/destinations/databricks.md index fc6454c399a6..3f4243a741f4 100644 --- a/docs/integrations/destinations/databricks.md +++ b/docs/integrations/destinations/databricks.md @@ -104,7 +104,7 @@ Each table will have the following columns: | `_airbyte_emitted_at` | timestamp | Data emission timestamp. | | Data fields from the source stream | various | All fields in the staging files will be expanded in the table. | -Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ## Getting started diff --git a/docs/integrations/destinations/gcs.md b/docs/integrations/destinations/gcs.md index 8bfd890f1727..975d629b48a6 100644 --- a/docs/integrations/destinations/gcs.md +++ b/docs/integrations/destinations/gcs.md @@ -102,7 +102,7 @@ Here is the available compression codecs: #### Data schema -Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ### CSV @@ -202,7 +202,7 @@ These parameters are related to the `ParquetOutputFormat`. See the [Java doc](ht #### Data schema -Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in Json schema is first converted to an Avro schema, then the Json object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the Json to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ## Getting started diff --git a/docs/integrations/destinations/google-sheets.md b/docs/integrations/destinations/google-sheets.md index 7b836e053508..f1824be795a1 100644 --- a/docs/integrations/destinations/google-sheets.md +++ b/docs/integrations/destinations/google-sheets.md @@ -28,7 +28,7 @@ Visit the [Google Support](https://support.google.com/accounts/answer/27441?hl=e **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **+ new destination**. 3. On the source setup page, select **Google Sheets** from the Source type dropdown and enter a name for this connector. 4. Select `Sign in with Google`. diff --git a/docs/integrations/destinations/kafka.md b/docs/integrations/destinations/kafka.md index 6645532b3cb6..1d9ac1d8bde2 100644 --- a/docs/integrations/destinations/kafka.md +++ b/docs/integrations/destinations/kafka.md @@ -54,7 +54,7 @@ Note that if you choose to use dynamic topic names, you will probably need to en #### Target topics -You can determine the topics to which messages are written via the `topic_pattern` configuration parameter. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.io/understanding-airbyte/namespaces) or stream they came from. +You can determine the topics to which messages are written via the `topic_pattern` configuration parameter. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.com/understanding-airbyte/namespaces) or stream they came from. To write all messages to a single hardcoded topic, enter its name in the `topic_pattern` field e.g: setting `topic_pattern` to `my-topic-name` will write all messages from all streams and namespaces to that topic. diff --git a/docs/integrations/destinations/mqtt.md b/docs/integrations/destinations/mqtt.md index e465ac5fdda5..d7f012097dbf 100644 --- a/docs/integrations/destinations/mqtt.md +++ b/docs/integrations/destinations/mqtt.md @@ -51,7 +51,7 @@ Airbyte should be allowed to write messages into topics. Based on the MQTT broke #### Target topics -You can determine the topics to which messages are written via the `topic_pattern` configuration parameter. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.io/understanding-airbyte/namespaces) or stream they came from. +You can determine the topics to which messages are written via the `topic_pattern` configuration parameter. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.com/understanding-airbyte/namespaces) or stream they came from. To write all messages to a single hardcoded topic, enter its name in the `topic_pattern` field e.g: setting `topic_pattern` to `path1/path2/my-topic-name` will write all messages from all streams and namespaces to that topic. diff --git a/docs/integrations/destinations/postgres.md b/docs/integrations/destinations/postgres.md index 7893d51ddb57..acacec90e80b 100644 --- a/docs/integrations/destinations/postgres.md +++ b/docs/integrations/destinations/postgres.md @@ -84,7 +84,7 @@ characters. **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **new destination**. 3. On the Set up the destination page, enter the name for the Postgres connector and select **Postgres** from the Destination type dropdown. diff --git a/docs/integrations/destinations/pulsar.md b/docs/integrations/destinations/pulsar.md index a40a25228886..9a44887da19f 100644 --- a/docs/integrations/destinations/pulsar.md +++ b/docs/integrations/destinations/pulsar.md @@ -56,7 +56,7 @@ Also, notice that the messages will be sent to topics based on the configured Pu #### Target topics -You can determine the topics to which messages are written via the `topic_pattern` configuration parameter in its corresponding Pulsar `topic_tenant`-`topic_namespace`. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.io/understanding-airbyte/namespaces) or stream they came from. +You can determine the topics to which messages are written via the `topic_pattern` configuration parameter in its corresponding Pulsar `topic_tenant`-`topic_namespace`. Messages can be written to either a hardcoded, pre-defined topic, or dynamically written to different topics based on the [namespace](https://docs.airbyte.com/understanding-airbyte/namespaces) or stream they came from. To write all messages to a single hardcoded topic, enter its name in the `topic_pattern` field e.g: setting `topic_pattern` to `my-topic-name` will write all messages from all streams and namespaces to that topic. diff --git a/docs/integrations/destinations/r2.md b/docs/integrations/destinations/r2.md index 37f25fea20bc..4f824a201359 100644 --- a/docs/integrations/destinations/r2.md +++ b/docs/integrations/destinations/r2.md @@ -26,7 +26,7 @@ to create an S3 bucket, or you can create bucket via R2 module of [dashboard](ht **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **+ new destination**. 3. On the destination setup page, select **R2** from the Destination type dropdown and enter a name for this connector. 4. Configure fields: @@ -175,7 +175,7 @@ Here is the available compression codecs: #### Data schema -Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ### CSV @@ -275,7 +275,7 @@ These parameters are related to the `ParquetOutputFormat`. See the [Java doc](ht #### Data schema -Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ## CHANGELOG diff --git a/docs/integrations/destinations/redshift.md b/docs/integrations/destinations/redshift.md index fca27d07da57..11c93184e779 100644 --- a/docs/integrations/destinations/redshift.md +++ b/docs/integrations/destinations/redshift.md @@ -65,7 +65,7 @@ GRANT usage, create on schema my_schema TO airflow_user; -- add create table per **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **+ new destination**. 3. On the destination setup page, select **Redshift** from the Destination type dropdown and enter a name for this connector. 4. Fill in all the required fields to use the INSERT or COPY strategy diff --git a/docs/integrations/destinations/s3-glue.md b/docs/integrations/destinations/s3-glue.md index be090b786004..d42c1f82fdda 100644 --- a/docs/integrations/destinations/s3-glue.md +++ b/docs/integrations/destinations/s3-glue.md @@ -39,7 +39,7 @@ Prepare the Glue database that will be used as destination, see [this](https://d **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **+ new destination**. 3. On the destination setup page, select **S3** from the Destination type dropdown and enter a name for this connector. 4. Configure fields: diff --git a/docs/integrations/destinations/s3.md b/docs/integrations/destinations/s3.md index 4af4a9db9f3b..eaa389363df5 100644 --- a/docs/integrations/destinations/s3.md +++ b/docs/integrations/destinations/s3.md @@ -32,7 +32,7 @@ NOTE: If the S3 cluster is not configured to use TLS, the connection to Amazon S **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Destinations**. In the top-right corner, click **+ new destination**. 3. On the destination setup page, select **S3** from the Destination type dropdown and enter a name for this connector. 4. Configure fields: @@ -216,7 +216,7 @@ Here is the available compression codecs: #### Data schema -Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). ### CSV @@ -316,7 +316,7 @@ These parameters are related to the `ParquetOutputFormat`. See the [Java doc](ht #### Data schema -Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.io/understanding-airbyte/json-avro-conversion). +Under the hood, an Airbyte data stream in JSON schema is first converted to an Avro schema, then the JSON object is converted to an Avro record, and finally the Avro record is outputted to the Parquet format. Because the data stream can come from any data source, the JSON to Avro conversion process has arbitrary rules and limitations. Learn more about how source data is converted to Avro and the current limitations [here](https://docs.airbyte.com/understanding-airbyte/json-avro-conversion). In order for everything to work correctly, it is also necessary that the user whose "S3 Key Id" and "S3 Access Key" are used have access to both the bucket and its contents. Policies to use: ```json diff --git a/docs/integrations/sources/airtable.md b/docs/integrations/sources/airtable.md index 9f52cfb52cbb..106172e761e2 100644 --- a/docs/integrations/sources/airtable.md +++ b/docs/integrations/sources/airtable.md @@ -13,7 +13,7 @@ This source syncs data from the [Airtable API](https://airtable.com/api). ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Airtable connector and select **Airtable** from the Source type dropdown. 4. Enter your `API Key` obtained by following [these steps](https://airtable.com/developers/web/guides/personal-access-tokens) diff --git a/docs/integrations/sources/alloydb.md b/docs/integrations/sources/alloydb.md index d15c5be9255b..aef6da0bf99e 100644 --- a/docs/integrations/sources/alloydb.md +++ b/docs/integrations/sources/alloydb.md @@ -80,7 +80,7 @@ This issue is tracked in [#9771](https://github.com/airbytehq/airbyte/issues/977 ### Step 2: Set up the AlloyDB connector in Airbyte -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **AlloyDB** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/amazon-ads.md b/docs/integrations/sources/amazon-ads.md index 5ded4dda4fe4..31344803f6de 100644 --- a/docs/integrations/sources/amazon-ads.md +++ b/docs/integrations/sources/amazon-ads.md @@ -24,7 +24,7 @@ To use the [Amazon Ads API](https://advertising.amazon.com/API/docs/en-us), you **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Amazon Ads** from the Source type dropdown and enter a name for this connector. 4. Click `Authenticate your Amazon Ads account`. diff --git a/docs/integrations/sources/amazon-seller-partner.md b/docs/integrations/sources/amazon-seller-partner.md index f597929a74fa..43754ae59332 100644 --- a/docs/integrations/sources/amazon-seller-partner.md +++ b/docs/integrations/sources/amazon-seller-partner.md @@ -30,7 +30,7 @@ Authenticating this Alpha connector is currently blocked. This is a known issue **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Amazon Seller Partner** from the Source type dropdown and enter a name for this connector. 4. Click `Authenticate your account`. diff --git a/docs/integrations/sources/amplitude.md b/docs/integrations/sources/amplitude.md index 72156b684400..7bfad1f009a0 100644 --- a/docs/integrations/sources/amplitude.md +++ b/docs/integrations/sources/amplitude.md @@ -8,7 +8,7 @@ To set up the Amplitude source connector, you'll need your Amplitude [`API Key` ## Set up the Amplitude source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Amplitude** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/appfollow.md b/docs/integrations/sources/appfollow.md index d8a19b02bcae..08f321c8b941 100644 --- a/docs/integrations/sources/appfollow.md +++ b/docs/integrations/sources/appfollow.md @@ -8,7 +8,7 @@ To set up the Appfollow source connector, you'll need your Appfollow `ext_id`, ` ## Set up the Appfollow source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Appfollow** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/asana.md b/docs/integrations/sources/asana.md index 3aa36d4d9a30..7f60a35ba5c4 100644 --- a/docs/integrations/sources/asana.md +++ b/docs/integrations/sources/asana.md @@ -12,7 +12,7 @@ Please follow these [steps](https://developers.asana.com/docs/personal-access-to ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+new source**. 3. Set the name for your source 4. Enter your `personal_access_token` diff --git a/docs/integrations/sources/bamboo-hr.md b/docs/integrations/sources/bamboo-hr.md index 0112dcf0fb49..597a92647354 100644 --- a/docs/integrations/sources/bamboo-hr.md +++ b/docs/integrations/sources/bamboo-hr.md @@ -44,7 +44,7 @@ This page contains the setup guide and reference information for the Bamboo HR s ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Bamboo HR connector and select **Bamboo HR** from the Source type dropdown. 3. Enter your `subdomain` diff --git a/docs/integrations/sources/bigcommerce.md b/docs/integrations/sources/bigcommerce.md index 127a2c36dfbc..1e29b6bbca9a 100644 --- a/docs/integrations/sources/bigcommerce.md +++ b/docs/integrations/sources/bigcommerce.md @@ -6,8 +6,6 @@ The BigCommerce source supports both Full Refresh and Incremental syncs. You can This source can sync data for the [BigCommerce API](https://developer.bigcommerce.com/api-docs/getting-started/making-requests). -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema This Source is capable of syncing the following core Streams: diff --git a/docs/integrations/sources/bing-ads.md b/docs/integrations/sources/bing-ads.md index 85505144c3ff..3e868f68f34b 100644 --- a/docs/integrations/sources/bing-ads.md +++ b/docs/integrations/sources/bing-ads.md @@ -26,7 +26,7 @@ The tenant is used in the authentication URL, for example: `https://login.micros **For Airbyte Cloud:** -1. Log in to your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. Log in to your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Bing Ads** from the **Source type** dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/braze.md b/docs/integrations/sources/braze.md index 49dddd08fa27..f4c2ccdc42ca 100644 --- a/docs/integrations/sources/braze.md +++ b/docs/integrations/sources/braze.md @@ -12,7 +12,7 @@ It is required to have an account on Braze to provide us with `URL` and `Rest AP ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Braze connector and select **Braze** from the Source type dropdown. 4. Fill in your `URL`, `Rest API Key` and `Start date` and then click **Set up source**. diff --git a/docs/integrations/sources/chargebee.md b/docs/integrations/sources/chargebee.md index e208071efd6b..9d11b7727c8a 100644 --- a/docs/integrations/sources/chargebee.md +++ b/docs/integrations/sources/chargebee.md @@ -8,7 +8,7 @@ To set up the Chargebee source connector, you'll need the [Chargebee API key](ht ## Set up the Chargebee connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Chargebee** from the Source type dropdown. 4. Enter the name for the Chargebee connector. diff --git a/docs/integrations/sources/chartmogul.md b/docs/integrations/sources/chartmogul.md index b8e9769ba7bd..70a52d3dec3e 100644 --- a/docs/integrations/sources/chartmogul.md +++ b/docs/integrations/sources/chartmogul.md @@ -14,7 +14,7 @@ This page contains the setup guide and reference information for the Chartmogul ### Step 2: Set up the Chartmogul connector in Airbyte **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Chartmogul** from the Source type dropdown and enter a name for this connector. 4. Enter the **API key** that you obtained. diff --git a/docs/integrations/sources/close-com.md b/docs/integrations/sources/close-com.md index 0d12d9f339f0..74c0d9fe3cd0 100644 --- a/docs/integrations/sources/close-com.md +++ b/docs/integrations/sources/close-com.md @@ -12,7 +12,7 @@ We recommend creating a restricted key specifically for Airbyte access. This wil ## Setup guide -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Close.com connector and select **Close.com** from the Source type dropdown. 4. Fill in the API Key and Start date fields and click **Set up source**. diff --git a/docs/integrations/sources/coda.md b/docs/integrations/sources/coda.md index b7c5438bd040..c39e90b19cc0 100755 --- a/docs/integrations/sources/coda.md +++ b/docs/integrations/sources/coda.md @@ -12,7 +12,7 @@ You can find or create authentication tokens within [Coda](https://coda.io/accou ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Coda connector and select **Coda** from the Source type dropdown. 4. Enter your `auth_token` - Coda Authentication Token with the necessary permissions \(described below\). diff --git a/docs/integrations/sources/commcare.md b/docs/integrations/sources/commcare.md index 045b2e89b5f5..6dd8fcebd647 100644 --- a/docs/integrations/sources/commcare.md +++ b/docs/integrations/sources/commcare.md @@ -10,7 +10,7 @@ This page guides you through the process of setting up the Commcare source conne ## Set up the Commcare source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Commcare** from the Source type dropdown. 4. Enter a name for your source. @@ -36,4 +36,4 @@ The Commcare source connector supports the following streams: ## Changelog | Version | Date | Pull Request | Subject | -| 0.1.0 | 2022-11-08 | [20220](https://github.com/airbytehq/airbyte/pull/20220) | Commcare Source Connector | \ No newline at end of file +| 0.1.0 | 2022-11-08 | [20220](https://github.com/airbytehq/airbyte/pull/20220) | Commcare Source Connector | diff --git a/docs/integrations/sources/commercetools.md b/docs/integrations/sources/commercetools.md index da1e99855751..66755961a829 100644 --- a/docs/integrations/sources/commercetools.md +++ b/docs/integrations/sources/commercetools.md @@ -6,8 +6,6 @@ The Commercetools source supports both Full Refresh and Incremental syncs. You c This source can sync data for the [Commercetools API](https://docs.commercetools.com/api/). -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema This Source is capable of syncing the following core Streams: diff --git a/docs/integrations/sources/courier.md b/docs/integrations/sources/courier.md index bcd963bf15fa..265e72520974 100644 --- a/docs/integrations/sources/courier.md +++ b/docs/integrations/sources/courier.md @@ -17,7 +17,7 @@ Generate an API key per the [Courier documentation](https://www.courier.com/docs ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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`. diff --git a/docs/integrations/sources/datadog.md b/docs/integrations/sources/datadog.md index a60734b4c36a..9d16433f5b2b 100644 --- a/docs/integrations/sources/datadog.md +++ b/docs/integrations/sources/datadog.md @@ -12,7 +12,7 @@ An API key is required as well as an API application key. See the [Datadog API a ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Datadog connector and select **Datadog** from the Source type dropdown. 4. Enter your `api_key` - Datadog API key. diff --git a/docs/integrations/sources/datascope.md b/docs/integrations/sources/datascope.md index 6daa5b66c0e3..3fa3285786bd 100644 --- a/docs/integrations/sources/datascope.md +++ b/docs/integrations/sources/datascope.md @@ -18,7 +18,7 @@ A DataScope account with access to the API. You can create a free account [here] ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 DataScope connector and select **DataScope** from the Source type dropdown. 4. Enter your `api_key`. @@ -61,4 +61,4 @@ GET https://www.mydatascope.com/api/external/locations | Version | Date | Pull Request | Subject | | :------ |:-----------|:----------------------------------------------------------| :------------- | -| 0.1.0 | 2022-10-31 | [#18725](https://github.com/airbytehq/airbyte/pull/18725) | Initial commit | \ No newline at end of file +| 0.1.0 | 2022-10-31 | [#18725](https://github.com/airbytehq/airbyte/pull/18725) | Initial commit | diff --git a/docs/integrations/sources/delighted.md b/docs/integrations/sources/delighted.md index fac11c324ad2..0fd192572a3d 100644 --- a/docs/integrations/sources/delighted.md +++ b/docs/integrations/sources/delighted.md @@ -8,7 +8,7 @@ To set up the Delighted source connector, you'll need the [Delighted API key](ht ## Set up the Delighted connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, enter the name for the Delighted connector and select **Delighted** from the Source type dropdown. 4. For **Since**, enter the date in a Unix Timestamp format. The data added on and after this date will be replicated. diff --git a/docs/integrations/sources/dremio.md b/docs/integrations/sources/dremio.md index a88265bfe1f2..0c3166340df8 100644 --- a/docs/integrations/sources/dremio.md +++ b/docs/integrations/sources/dremio.md @@ -4,8 +4,6 @@ The Dremio source supports Full Refresh sync. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema Several output streams are available from this source: diff --git a/docs/integrations/sources/facebook-marketing.md b/docs/integrations/sources/facebook-marketing.md index 191558d8e8aa..8eafd68b344d 100644 --- a/docs/integrations/sources/facebook-marketing.md +++ b/docs/integrations/sources/facebook-marketing.md @@ -16,7 +16,7 @@ This page guides you through the process of setting up the Facebook Marketing so To set up Facebook Marketing as a source in Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Facebook Marketing** from the **Source type** dropdown. 4. For Name, enter a name for the Facebook Marketing connector. diff --git a/docs/integrations/sources/facebook-pages.md b/docs/integrations/sources/facebook-pages.md index 46c6a513ae9b..2289560fb2e7 100644 --- a/docs/integrations/sources/facebook-pages.md +++ b/docs/integrations/sources/facebook-pages.md @@ -30,7 +30,7 @@ After all the steps, it should look something like this ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Facebook Pages connector and select **Facebook Pages** from the Source type dropdown. 4. Fill in Page Access Token with Long-Lived Page Token diff --git a/docs/integrations/sources/fastbill.md b/docs/integrations/sources/fastbill.md index 6979873f96bf..05cf2c4793bd 100644 --- a/docs/integrations/sources/fastbill.md +++ b/docs/integrations/sources/fastbill.md @@ -14,7 +14,7 @@ You can find your Project ID and find or create an API key within [Fastbill](htt ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Fastbill connector and select **Fastbill** from the Source type dropdown. 4. Enter your `username` - Fastbill username/email. @@ -61,4 +61,4 @@ The Fastbill source connector supports the following [sync modes](https://docs.a | Version | Date | Pull Request | Subject | |:--------|:------------|:---------------------------------------------------------|:--------------------------------------------------| -| 0.1.0 | 2022-10-TBA | [18522](https://github.com/airbytehq/airbyte/pull/18593) | New Source: Fastbill | \ No newline at end of file +| 0.1.0 | 2022-10-TBA | [18522](https://github.com/airbytehq/airbyte/pull/18593) | New Source: Fastbill | diff --git a/docs/integrations/sources/freshdesk.md b/docs/integrations/sources/freshdesk.md index 24e94e7e55b2..680a97473663 100644 --- a/docs/integrations/sources/freshdesk.md +++ b/docs/integrations/sources/freshdesk.md @@ -8,7 +8,7 @@ To set up the Freshdesk source connector, you'll need the Freshdesk [domain URL] ## Set up the Freshdesk connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Freshdesk** from the Source type dropdown. 4. Enter the name for the Freshdesk connector. diff --git a/docs/integrations/sources/github.md b/docs/integrations/sources/github.md index c8e185637744..ee5ce209a099 100644 --- a/docs/integrations/sources/github.md +++ b/docs/integrations/sources/github.md @@ -39,7 +39,7 @@ Log into [GitHub](https://github.com) and then generate a [personal access token **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **GitHub** from the Source type dropdown and enter a name for this connector. 4. Click `Authenticate your GitHub account` by selecting Oauth or Personal Access Token for Authentication. diff --git a/docs/integrations/sources/gitlab.md b/docs/integrations/sources/gitlab.md index dc278f6d08cb..1ecce3b7ab9c 100644 --- a/docs/integrations/sources/gitlab.md +++ b/docs/integrations/sources/gitlab.md @@ -39,7 +39,7 @@ Log into [GitLab](https://gitlab.com) and then generate a [personal access token **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **GitLab** from the Source type dropdown and enter a name for this connector. 4. Click `Authenticate your GitLab account` by selecting Oauth or Personal Access Token for Authentication. diff --git a/docs/integrations/sources/glassfrog.md b/docs/integrations/sources/glassfrog.md index 08d3b2cc0ff5..b6d307810185 100644 --- a/docs/integrations/sources/glassfrog.md +++ b/docs/integrations/sources/glassfrog.md @@ -4,7 +4,7 @@ The Glassfrog source supports only Full Refresh syncs. This source can sync data for the [Glassfrog API](https://documenter.getpostman.com/view/1014385/glassfrog-api-v3/2SJViY). -This Source Connector is based on the [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). +This Source Connector is based on the [Airbyte CDK](https://docs.airbyte.com/connector-development/cdk-python). ### Output schema diff --git a/docs/integrations/sources/google-ads.md b/docs/integrations/sources/google-ads.md index 2683080268dc..b07aca4b54ea 100644 --- a/docs/integrations/sources/google-ads.md +++ b/docs/integrations/sources/google-ads.md @@ -35,7 +35,7 @@ When you apply for a token, make sure to mention: To set up Google Ads as a source in Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Google Ads** from the Source type dropdown. 4. Enter a **Name** for your source. diff --git a/docs/integrations/sources/google-analytics-data-api.md b/docs/integrations/sources/google-analytics-data-api.md index 9ef106cbfed9..7d7ab05358a6 100644 --- a/docs/integrations/sources/google-analytics-data-api.md +++ b/docs/integrations/sources/google-analytics-data-api.md @@ -41,7 +41,7 @@ To determine a Google Analytics 4 [Property ID](https://developers.google.com/an **For Airbyte Cloud:** -1. [Login to your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Login to your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Google Analytics 4 (GA4)** from the Source type dropdown and enter a name for this connector. 4. Click `Authenticate your account` by selecting Oauth or Service Account for Authentication. diff --git a/docs/integrations/sources/google-analytics-v4.md b/docs/integrations/sources/google-analytics-v4.md index f1c7a97d13a1..627135755da0 100644 --- a/docs/integrations/sources/google-analytics-v4.md +++ b/docs/integrations/sources/google-analytics-v4.md @@ -11,7 +11,7 @@ This connector supports Universal Analytics properties through the [Reporting AP To set up Google Analytics as a source in Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Google Analytics** from the **Source type** dropdown. 4. For Name, enter a name for the Google Analytics connector. diff --git a/docs/integrations/sources/google-pagespeed-insights.md b/docs/integrations/sources/google-pagespeed-insights.md index 72a09001d423..579642a7283d 100644 --- a/docs/integrations/sources/google-pagespeed-insights.md +++ b/docs/integrations/sources/google-pagespeed-insights.md @@ -9,7 +9,7 @@ This page guides you through the process of setting up the Google PageSpeed Insi ## Set up the Google PageSpeed Insights source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Google PageSpeed Insights** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/google-search-console.md b/docs/integrations/sources/google-search-console.md index 07b2f9471fb9..029b11eaecd7 100644 --- a/docs/integrations/sources/google-search-console.md +++ b/docs/integrations/sources/google-search-console.md @@ -67,7 +67,7 @@ At the end of this process, you should have JSON credentials to this Google Serv **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 google search console connector and select **google search console** from the Source type dropdown. 4. Click Authenticate your account to sign in with Google and authorize your account. diff --git a/docs/integrations/sources/google-sheets.md b/docs/integrations/sources/google-sheets.md index ce3adce374bd..c8566a49c1ad 100644 --- a/docs/integrations/sources/google-sheets.md +++ b/docs/integrations/sources/google-sheets.md @@ -13,7 +13,7 @@ The Google Sheets source connector pulls data from a single Google Sheets spread To set up Google Sheets as a source in Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Google Sheets** from the **Source type** dropdown. 4. Enter a name for the Google Sheets connector. diff --git a/docs/integrations/sources/google-webfonts.md b/docs/integrations/sources/google-webfonts.md index b3a5e69ab01e..8b2eb2c5cbec 100644 --- a/docs/integrations/sources/google-webfonts.md +++ b/docs/integrations/sources/google-webfonts.md @@ -22,7 +22,7 @@ Just pass the generated API key and optional parameters for establishing the con ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Google-webfonts connector and select **Google-webfonts** from the Source type dropdown. 4. Enter your `api_key`. @@ -65,4 +65,4 @@ Google Webfont's [API reference](https://developers.google.com/fonts/docs/develo | Version | Date | Pull Request | Subject | | :------ | :--------- | :----------------------------------------------------- | :------------- | -| 0.1.0 | 2022-10-26 | [Init](https://github.com/airbytehq/airbyte/pull/18496)| Initial commit | \ No newline at end of file +| 0.1.0 | 2022-10-26 | [Init](https://github.com/airbytehq/airbyte/pull/18496)| Initial commit | diff --git a/docs/integrations/sources/greenhouse.md b/docs/integrations/sources/greenhouse.md index 0d6bdbeb414a..d175b2aadcbc 100644 --- a/docs/integrations/sources/greenhouse.md +++ b/docs/integrations/sources/greenhouse.md @@ -8,7 +8,7 @@ To set up the Greenhouse source connector, you'll need the [Harvest API key](htt ## Set up the Greenhouse connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Greenhouse** from the Source type dropdown. 4. Enter the name for the Greenhouse connector. diff --git a/docs/integrations/sources/gutendex.md b/docs/integrations/sources/gutendex.md index ada413dfbce8..fa026dd5da4b 100644 --- a/docs/integrations/sources/gutendex.md +++ b/docs/integrations/sources/gutendex.md @@ -53,7 +53,7 @@ The source is capable of syncing the results stream. ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Gutendex** from the Source type dropdown. 4. Click **Set up source**. diff --git a/docs/integrations/sources/harvest.md b/docs/integrations/sources/harvest.md index dfeced615aa5..b59f863e8a0e 100644 --- a/docs/integrations/sources/harvest.md +++ b/docs/integrations/sources/harvest.md @@ -11,7 +11,7 @@ To set up the Harvest source connector, you'll need the [Harvest Account ID and **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces). +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces). 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Harvest** from the Source type dropdown. 4. Enter the name for the Harvest connector. diff --git a/docs/integrations/sources/hubspot.md b/docs/integrations/sources/hubspot.md index 1d433009fa68..21d5eaa24ff1 100644 --- a/docs/integrations/sources/hubspot.md +++ b/docs/integrations/sources/hubspot.md @@ -31,7 +31,7 @@ You can use OAuth, API key, or Private App to authenticate your HubSpot account. ## Set up the HubSpot source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **HubSpot** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/insightly.md b/docs/integrations/sources/insightly.md index 3f77f97ed97f..73ec61a92505 100644 --- a/docs/integrations/sources/insightly.md +++ b/docs/integrations/sources/insightly.md @@ -4,7 +4,7 @@ This page guides you through the process of setting up the Insightly source conn ## Set up the Insightly connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Insightly** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/instagram.md b/docs/integrations/sources/instagram.md index 27e4c09cecfc..5765d7ee3992 100644 --- a/docs/integrations/sources/instagram.md +++ b/docs/integrations/sources/instagram.md @@ -25,7 +25,7 @@ Generate access tokens with the following permissions: **For Airbyte Cloud:** -1. Log in to your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. Log in to your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Instagram** from the **Source type** dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/intercom.md b/docs/integrations/sources/intercom.md index 00ecaef64650..87f3c1c56ffb 100644 --- a/docs/integrations/sources/intercom.md +++ b/docs/integrations/sources/intercom.md @@ -4,7 +4,7 @@ This page guides you through the process of setting up the Intercom source conne ## Set up the Intercom connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Intercom** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/iterable.md b/docs/integrations/sources/iterable.md index 33956fc29649..439de4af99e4 100644 --- a/docs/integrations/sources/iterable.md +++ b/docs/integrations/sources/iterable.md @@ -8,7 +8,7 @@ To set up the Iterable source connector, you'll need the Iterable [`Server-side` ## Set up the Iterable connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Iterable** from the Source type dropdown. 4. Enter the name for the Iterable connector. diff --git a/docs/integrations/sources/jira.md b/docs/integrations/sources/jira.md index db9966bc0b3f..0964ac2f697e 100644 --- a/docs/integrations/sources/jira.md +++ b/docs/integrations/sources/jira.md @@ -18,7 +18,7 @@ This page contains the setup guide and reference information for the Jira source **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Jira** from the Source type dropdown and enter a name for this connector. 4. Enter the **API Token** that you have created. diff --git a/docs/integrations/sources/klaviyo.md b/docs/integrations/sources/klaviyo.md index 810b2fdcfea4..fc136345fe15 100644 --- a/docs/integrations/sources/klaviyo.md +++ b/docs/integrations/sources/klaviyo.md @@ -9,7 +9,7 @@ To set up the Klaviyo source connector, you'll need the [Klaviyo Private API key ## Set up the Klaviyo connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Klaviyo** from the Source type dropdown. 4. Enter the name for the Klaviyo connector. diff --git a/docs/integrations/sources/linkedin-ads.md b/docs/integrations/sources/linkedin-ads.md index a6cdd7d1a22c..82116b8e8f1f 100644 --- a/docs/integrations/sources/linkedin-ads.md +++ b/docs/integrations/sources/linkedin-ads.md @@ -102,7 +102,7 @@ To edit these roles, sign in to Campaign Manager and follow [these instructions] **For Airbyte Cloud:** -1. [Login to your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Login to your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **LinkedIn Ads** from the Source type dropdown and enter a name for this connector. 4. Add `Start Date` - the starting point for your data replication. diff --git a/docs/integrations/sources/linkedin-pages.md b/docs/integrations/sources/linkedin-pages.md index 5801bcfff1f3..471b040e4c9e 100644 --- a/docs/integrations/sources/linkedin-pages.md +++ b/docs/integrations/sources/linkedin-pages.md @@ -4,7 +4,7 @@ The LinkedIn Pages source only supports Full Refresh for now. Incremental Sync will be coming soon. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). Airbyte uses [LinkedIn Marketing Developer Platform - API](https://docs.microsoft.com/en-us/linkedin/marketing/integrations/marketing-integrations-overview) to fetch data from LinkedIn Pages. +Airbyte uses [LinkedIn Marketing Developer Platform - API](https://docs.microsoft.com/en-us/linkedin/marketing/integrations/marketing-integrations-overview) to fetch data from LinkedIn Pages. ### Output schema @@ -84,7 +84,7 @@ The source LinkedIn Pages can use either the `client_id`, `client_secret` and `r * Review/agree to legal terms and create app * Review the **Auth** tab: * **Save your `client_id` and `client_secret`** \(for later steps\) - * Oauth 2.0 settings: Provide a `redirect_uri` \(for later steps\): `https://airbyte.io` + * Oauth 2.0 settings: Provide a `redirect_uri` \(for later steps\): `https://airbyte.com` 3. **Verify App**: * In the **Settings** tab of your app dashboard, you'll see a **Verify** button. Click that button! @@ -110,4 +110,4 @@ The source LinkedIn Pages can use either the `client_id`, `client_secret` and `r | Version | Date | Pull Request | Subject | | :------ | :--------- | :------------------------------------------------------- | :--------------------------------------------------------- | -| 0.1.0 | 2022-08-11 | [13098](https://github.com/airbytehq/airbyte/pull/13098) | Initial Release | \ No newline at end of file +| 0.1.0 | 2022-08-11 | [13098](https://github.com/airbytehq/airbyte/pull/13098) | Initial Release | diff --git a/docs/integrations/sources/linnworks.md b/docs/integrations/sources/linnworks.md index ce6c73a99a3a..ef1da0d98548 100644 --- a/docs/integrations/sources/linnworks.md +++ b/docs/integrations/sources/linnworks.md @@ -4,7 +4,7 @@ Linnworks source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). Airbyte uses [Linnworks API](https://apps.linnworks.net/Api) to fetch data from Linnworks. +Airbyte uses [Linnworks API](https://apps.linnworks.net/Api) to fetch data from Linnworks. ### Output schema diff --git a/docs/integrations/sources/lokalise.md b/docs/integrations/sources/lokalise.md index 2dff7dd3fe5f..aa4ab5ef7f07 100644 --- a/docs/integrations/sources/lokalise.md +++ b/docs/integrations/sources/lokalise.md @@ -14,7 +14,7 @@ You can find your Project ID and find or create an API key within [Lokalise](htt ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Lokalise connector and select **Lokalise** from the Source type dropdown. 4. Enter your `project_id` - Lokalise Project ID. diff --git a/docs/integrations/sources/mailchimp.md b/docs/integrations/sources/mailchimp.md index 06e16dbd1b50..2fc466385300 100644 --- a/docs/integrations/sources/mailchimp.md +++ b/docs/integrations/sources/mailchimp.md @@ -8,7 +8,7 @@ You can use [OAuth](https://mailchimp.com/developer/marketing/guides/access-user ## Set up the Mailchimp source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Mailchimp** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/marketo.md b/docs/integrations/sources/marketo.md index e4b57ddb4914..92d2da4ca04f 100644 --- a/docs/integrations/sources/marketo.md +++ b/docs/integrations/sources/marketo.md @@ -47,7 +47,7 @@ We're almost there! Armed with your Endpoint & Identity URLs and your Client ID **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Marketo connector and select **Marketo** from the Source type dropdown. 4. Enter the start date, domain URL, client ID and secret diff --git a/docs/integrations/sources/mixpanel.md b/docs/integrations/sources/mixpanel.md index c90209c7e55e..31d41825c107 100644 --- a/docs/integrations/sources/mixpanel.md +++ b/docs/integrations/sources/mixpanel.md @@ -8,7 +8,7 @@ To set up the Harvest source connector, you'll need a Mixpanel [Service Account] ## Set up the Mixpanel connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Mixpanel** from the Source type dropdown. 4. Enter the name for the Mixpanel connector. diff --git a/docs/integrations/sources/monday.md b/docs/integrations/sources/monday.md index 6fa6f8ea4e1a..1b0839444633 100644 --- a/docs/integrations/sources/monday.md +++ b/docs/integrations/sources/monday.md @@ -10,7 +10,7 @@ You can get the API token for Monday by going to Profile picture (bottom left co ## Setup guide -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Monday connector and select **Monday** from the Source type dropdown. 4. Fill in your API Key or authenticate using OAuth and then click **Set up source**. diff --git a/docs/integrations/sources/netsuite.md b/docs/integrations/sources/netsuite.md index 8747c21b9950..4183b4722c87 100644 --- a/docs/integrations/sources/netsuite.md +++ b/docs/integrations/sources/netsuite.md @@ -83,7 +83,7 @@ Also you have properly **Configured Account** with **Correct Permissions** and * ### Step 3: Set up the source connector in Airbyte ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **NetSuite** from the Source type dropdown and enter a name for this connector. 4. Add **Realm** diff --git a/docs/integrations/sources/notion.md b/docs/integrations/sources/notion.md index bb93c2f5b91a..a07daa4f422c 100644 --- a/docs/integrations/sources/notion.md +++ b/docs/integrations/sources/notion.md @@ -27,7 +27,7 @@ You must be the owner of a Notion workspace to create a new integration. **For Airbyte Cloud:** -1. Log in to your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. Log in to your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Notion** from the **Source type** dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/okta.md b/docs/integrations/sources/okta.md index eaafd372a01f..b4c95ad5572b 100644 --- a/docs/integrations/sources/okta.md +++ b/docs/integrations/sources/okta.md @@ -28,7 +28,7 @@ Okta is the complete identity solution for all your apps and people that’s uni ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Okta** from the Source type dropdown and enter a name for this connector. 4. Add **Name** diff --git a/docs/integrations/sources/paypal-transaction.md b/docs/integrations/sources/paypal-transaction.md index 6b2d4f35cb88..460ab8c6014b 100644 --- a/docs/integrations/sources/paypal-transaction.md +++ b/docs/integrations/sources/paypal-transaction.md @@ -22,7 +22,7 @@ Our Paypal Transactions Source Connector does not support OAuth at this time due **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Paypal Transaction connector and select **Paypal Transaction** from the Source type dropdown. 4. Enter your client id diff --git a/docs/integrations/sources/pexels-api.md b/docs/integrations/sources/pexels-api.md index 19bcb4f26e6b..9a6980f8b702 100644 --- a/docs/integrations/sources/pexels-api.md +++ b/docs/integrations/sources/pexels-api.md @@ -24,7 +24,7 @@ Just pass the generated API key and optional parameters for establishing the con ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Pexels-API connector and select **Pexels-API** from the Source type dropdown. 4. Enter your `api_key`. diff --git a/docs/integrations/sources/pinterest.md b/docs/integrations/sources/pinterest.md index 6738b53b8fe7..63fbe581edfc 100644 --- a/docs/integrations/sources/pinterest.md +++ b/docs/integrations/sources/pinterest.md @@ -11,7 +11,7 @@ To set up the Pinterest source connector with Airbyte Open Source, you'll need y **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Pinterest** from the Source type dropdown. 4. Enter the name for the Pinterest connector. diff --git a/docs/integrations/sources/postgres.md b/docs/integrations/sources/postgres.md index 697973628aaf..7acae266674f 100644 --- a/docs/integrations/sources/postgres.md +++ b/docs/integrations/sources/postgres.md @@ -86,7 +86,7 @@ This issue is tracked in [#9771](https://github.com/airbytehq/airbyte/issues/977 ### Step 2: Set up the Postgres connector in Airbyte -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Postgres** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/posthog.md b/docs/integrations/sources/posthog.md index e3f723670957..d83e9fb62aa4 100644 --- a/docs/integrations/sources/posthog.md +++ b/docs/integrations/sources/posthog.md @@ -16,7 +16,7 @@ This page contains the setup guide and reference information for the PostHog sou ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 PostHog connector and select **PostHog** from the Source type dropdown. 4. Enter your `apikey`. diff --git a/docs/integrations/sources/postmarkapp.md b/docs/integrations/sources/postmarkapp.md index 76e23fbf4a85..88b71a76a60a 100644 --- a/docs/integrations/sources/postmarkapp.md +++ b/docs/integrations/sources/postmarkapp.md @@ -30,7 +30,7 @@ Account-API ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Postmarkapp** from the Source type dropdown. 4. Click **Set up source**. @@ -56,4 +56,4 @@ The Postmarkapp source connector supports the following [sync modes](https://doc | Version | Date | Pull Request | Subject | | :------ |:-----|:-------------| :----------------------------------------- | -| 0.1.0 | 2022-11-09 | 18220 | 🎉 New Source: Postmarkapp API [low-code CDK] | \ No newline at end of file +| 0.1.0 | 2022-11-09 | 18220 | 🎉 New Source: Postmarkapp API [low-code CDK] | diff --git a/docs/integrations/sources/prestashop.md b/docs/integrations/sources/prestashop.md index f58caa5319b4..e31e4527030c 100644 --- a/docs/integrations/sources/prestashop.md +++ b/docs/integrations/sources/prestashop.md @@ -19,7 +19,7 @@ This page contains the setup guide and reference information for the PrestaShop **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **PrestaShop** from the Source type dropdown and enter a name for this connector. 4. Enter the **Access Key** that you obtained. diff --git a/docs/integrations/sources/punk-api.md b/docs/integrations/sources/punk-api.md index 1488ee743695..27d4871ada04 100644 --- a/docs/integrations/sources/punk-api.md +++ b/docs/integrations/sources/punk-api.md @@ -17,7 +17,7 @@ Api key is not required for this connector to work,But a dummy key need to be pa ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Punk-API connector and select **Punk-API** from the Source type dropdown. 4. Enter your dummy `api_key`. @@ -61,4 +61,4 @@ Punk API's [API reference](https://punkapi.com/documentation/v2) has v2 at prese | Version | Date | Pull Request | Subject | | :------ | :--------- | :----------------------------------------------------- | :------------- | -| 0.1.0 | 2022-10-31 | [Init](https://github.com/airbytehq/airbyte/pull/)| Initial commit | \ No newline at end of file +| 0.1.0 | 2022-10-31 | [Init](https://github.com/airbytehq/airbyte/pull/)| Initial commit | diff --git a/docs/integrations/sources/qualaroo.md b/docs/integrations/sources/qualaroo.md index 85ccd44e4020..1c4b53eda244 100644 --- a/docs/integrations/sources/qualaroo.md +++ b/docs/integrations/sources/qualaroo.md @@ -4,8 +4,6 @@ The Qualaroo source supports Full Refresh syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema Several output streams are available from this source: diff --git a/docs/integrations/sources/railz.md b/docs/integrations/sources/railz.md index e65532df9848..b3ca0f27c4ff 100644 --- a/docs/integrations/sources/railz.md +++ b/docs/integrations/sources/railz.md @@ -20,7 +20,7 @@ Generate API key [on the dashboard](https://dashboard.railz.ai/developers/api-ke **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account; +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account; 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**; 3. On the source setup page, select **Railz** from the Source type dropdown and enter a name for this connector; 4. Enter `Client ID (client_id)`; diff --git a/docs/integrations/sources/recharge.md b/docs/integrations/sources/recharge.md index 62c36d632764..ce493ab335b5 100644 --- a/docs/integrations/sources/recharge.md +++ b/docs/integrations/sources/recharge.md @@ -20,7 +20,7 @@ Please read [How to generate your API token](https://support.rechargepayments.co **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Recharge** from the Source type dropdown and enter a name for this connector. 4. Choose required `Start date` diff --git a/docs/integrations/sources/recruitee.md b/docs/integrations/sources/recruitee.md index 2a93125a4317..310ba261d004 100644 --- a/docs/integrations/sources/recruitee.md +++ b/docs/integrations/sources/recruitee.md @@ -14,7 +14,7 @@ You can find your Company ID and find or create an API key within [Recruitee](ht ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Recruitee connector and select **Recruitee** from the Source type dropdown. 4. Enter your `company_id` - Recruitee Company ID. diff --git a/docs/integrations/sources/s3.md b/docs/integrations/sources/s3.md index b9ecac26aeea..486cf9a44717 100644 --- a/docs/integrations/sources/s3.md +++ b/docs/integrations/sources/s3.md @@ -17,7 +17,7 @@ Define file pattern, see the [Path Patterns section](s3.md#path-patterns) **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click ****. In the top-right corner, click **+new source/destination**. 3. On the Set up the source/destination page, enter the name for the `connector name` connector and select **connector name** from the `Source/Destination` type dropdown. 4. Set `dataset` appropriately. This will be the name of the table in the destination. diff --git a/docs/integrations/sources/salesforce.md b/docs/integrations/sources/salesforce.md index 3363488ad739..db354e3ae350 100644 --- a/docs/integrations/sources/salesforce.md +++ b/docs/integrations/sources/salesforce.md @@ -43,7 +43,7 @@ To create a dedicated read only Salesforce user: To set up Salesforce as a source in Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **Salesforce** from the **Source type** dropdown. 4. For Name, enter a name for the Salesforce connector. diff --git a/docs/integrations/sources/search-metrics.md b/docs/integrations/sources/search-metrics.md index 324c7a02c4d6..5d49b4bdb967 100644 --- a/docs/integrations/sources/search-metrics.md +++ b/docs/integrations/sources/search-metrics.md @@ -4,8 +4,6 @@ The SearchMetrics source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema Several output streams are available from this source: diff --git a/docs/integrations/sources/sendgrid.md b/docs/integrations/sources/sendgrid.md index 08cb4c4d52ea..32b1492f71d3 100644 --- a/docs/integrations/sources/sendgrid.md +++ b/docs/integrations/sources/sendgrid.md @@ -18,7 +18,7 @@ This page contains the setup guide and reference information for the Sendgrid so ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Sendgrid connector and select **Sendgrid** from the Source type dropdown. 4. Enter your `apikey`. diff --git a/docs/integrations/sources/senseforce.md b/docs/integrations/sources/senseforce.md index c8d161a823e7..ba04db94493a 100644 --- a/docs/integrations/sources/senseforce.md +++ b/docs/integrations/sources/senseforce.md @@ -28,7 +28,7 @@ The Senseforce Airbyte connector allows to export custom datasets built bei Sens ## Set up the Senseforce source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Senseforce** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/sentry.md b/docs/integrations/sources/sentry.md index d539bd4294c5..28c3518c8d39 100644 --- a/docs/integrations/sources/sentry.md +++ b/docs/integrations/sources/sentry.md @@ -8,7 +8,7 @@ To set up the Sentry source connector, you'll need the Sentry [project name](htt ## Set up the Sentry connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account or navigate to the Airbyte Open Source dashboard. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account or navigate to the Airbyte Open Source dashboard. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Sentry** from the Source type dropdown. 4. Enter the name for the Sentry connector. diff --git a/docs/integrations/sources/sftp.md b/docs/integrations/sources/sftp.md index 0f5586458df2..ca19d406af57 100644 --- a/docs/integrations/sources/sftp.md +++ b/docs/integrations/sources/sftp.md @@ -24,7 +24,7 @@ Server will now allow access to anyone who can prove they have the corresponding #### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 SFTP connector and select **SFTP** from the Source type dropdown. 4. Enter your `User Name`, `Host Address`, `Port` diff --git a/docs/integrations/sources/shopify.md b/docs/integrations/sources/shopify.md index fd410ccee5e1..b355074a08e6 100644 --- a/docs/integrations/sources/shopify.md +++ b/docs/integrations/sources/shopify.md @@ -18,8 +18,6 @@ The Shopify source supports both Full Refresh and Incremental syncs. You can cho This source can sync data for the [Shopify REST API](https://shopify.dev/api/admin-rest) and the [Shopify GraphQl API](https://shopify.dev/api/admin-graphql). -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ## Troubleshooting Check out common troubleshooting issues for the Shopify source connector on our Discourse [here](https://discuss.airbyte.io/tags/c/connector/11/source-shopify). diff --git a/docs/integrations/sources/shortio.md b/docs/integrations/sources/shortio.md index 27a9a0b43a52..4bf26cee51fe 100644 --- a/docs/integrations/sources/shortio.md +++ b/docs/integrations/sources/shortio.md @@ -6,8 +6,6 @@ The Shopify source supports both Full Refresh and Incremental syncs. You can cho This source can sync data for the [Shortio API](https://developers.short.io/reference). -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema This Source is capable of syncing the following Streams: diff --git a/docs/integrations/sources/slack.md b/docs/integrations/sources/slack.md index a84035d19f7e..face95ba0658 100644 --- a/docs/integrations/sources/slack.md +++ b/docs/integrations/sources/slack.md @@ -72,7 +72,7 @@ We recommend creating a restricted, read-only key specifically for Airbyte acces **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Slack connector and select **Slack** from the Source type dropdown. 4. Select `Authenticate your account` and log in and Authorize to the Slack account. diff --git a/docs/integrations/sources/smartsheets.md b/docs/integrations/sources/smartsheets.md index 8f90a55a949e..7706726c51dd 100644 --- a/docs/integrations/sources/smartsheets.md +++ b/docs/integrations/sources/smartsheets.md @@ -33,7 +33,7 @@ You'll also need the ID of the Spreadsheet you'd like to sync. Unlike Google She **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Smartsheets connector and select **Smartsheets** from the Source type dropdown. 4. Authenticate via OAuth2.0 using the API access token from Prerequisites diff --git a/docs/integrations/sources/snapchat-marketing.md b/docs/integrations/sources/snapchat-marketing.md index 4bcc23673a17..fb6ec78b381c 100644 --- a/docs/integrations/sources/snapchat-marketing.md +++ b/docs/integrations/sources/snapchat-marketing.md @@ -57,7 +57,7 @@ The useful link to Authentication process is [here](https://marketingapi.snapcha **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Snapchat Marketing** from the Source type dropdown and enter a name for this connector. 4. lick `Authenticate your account`. diff --git a/docs/integrations/sources/spacex-api.md b/docs/integrations/sources/spacex-api.md index a366856e9f77..59bac3bd742d 100644 --- a/docs/integrations/sources/spacex-api.md +++ b/docs/integrations/sources/spacex-api.md @@ -17,7 +17,7 @@ No prerequisites, but a dummy api_key is required as it enhances security in fut ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 SpaceX-API connector and select **Spacex-API** from the Source type dropdown. 4. Enter your `api_key`. diff --git a/docs/integrations/sources/square.md b/docs/integrations/sources/square.md index f460aa67b22f..09e29b7c135c 100644 --- a/docs/integrations/sources/square.md +++ b/docs/integrations/sources/square.md @@ -17,7 +17,7 @@ To set up the Square source connector with Airbyte, you'll need to create your S ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Square connector and select **Square** from the Source type dropdown. 4. Choose authentication method: diff --git a/docs/integrations/sources/stripe.md b/docs/integrations/sources/stripe.md index 0fda24d19eaa..7f26472164c4 100644 --- a/docs/integrations/sources/stripe.md +++ b/docs/integrations/sources/stripe.md @@ -13,7 +13,7 @@ This page guides you through the process of setting up the Stripe source connect ## Set up the Stripe source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Stripe** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/surveycto.md b/docs/integrations/sources/surveycto.md index 717cc9e8b4c3..aee661eae3fd 100644 --- a/docs/integrations/sources/surveycto.md +++ b/docs/integrations/sources/surveycto.md @@ -17,7 +17,7 @@ This page guides you through the process of setting up the SurveyCTO source conn - give your user an API consumer permission to the existing role or create a user with that role and permission. ## Set up the SurveyCTO source connection -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Survey CTO** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/surveymonkey.md b/docs/integrations/sources/surveymonkey.md index 758d7b4f6ca2..6dcc46f9c667 100644 --- a/docs/integrations/sources/surveymonkey.md +++ b/docs/integrations/sources/surveymonkey.md @@ -25,7 +25,7 @@ Please read this [docs](https://developer.surveymonkey.com/api/v3/#getting-start **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **SurveyMonkey** from the Source type dropdown and enter a name for this connector. 4. lick `Authenticate your account`. diff --git a/docs/integrations/sources/tempo.md b/docs/integrations/sources/tempo.md index bdd5843147bc..087246190f98 100644 --- a/docs/integrations/sources/tempo.md +++ b/docs/integrations/sources/tempo.md @@ -16,7 +16,7 @@ Go to **Tempo > Settings**, scroll down to **Data Access** and select **API i ## Step 2: Set up the Tempo connector in Airbyte -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Tempo connector and select **Tempo** from the Source type dropdown. 4. Enter your API token that you obtained from Tempo. diff --git a/docs/integrations/sources/the-guardian-api.md b/docs/integrations/sources/the-guardian-api.md index aea779c6ed95..94b866647926 100644 --- a/docs/integrations/sources/the-guardian-api.md +++ b/docs/integrations/sources/the-guardian-api.md @@ -79,7 +79,7 @@ The source is capable of syncing the content stream. ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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, select **The Guardian API** from the Source type dropdown. 4. Enter your api_key (mandatory) and any other optional parameters as per your requirements. diff --git a/docs/integrations/sources/tiktok-marketing.md b/docs/integrations/sources/tiktok-marketing.md index 7f5c1c52d1b3..a44982fc1ea8 100644 --- a/docs/integrations/sources/tiktok-marketing.md +++ b/docs/integrations/sources/tiktok-marketing.md @@ -35,7 +35,7 @@ To access the Sandbox environment: **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Tiktok Marketing** from the Source type dropdown and enter a name for this connector. 4. Select `OAuth2.0` Authorization method, then click `Authenticate your account`. diff --git a/docs/integrations/sources/tmdb.md b/docs/integrations/sources/tmdb.md index 75c2d5bbf499..472fdaca8391 100644 --- a/docs/integrations/sources/tmdb.md +++ b/docs/integrations/sources/tmdb.md @@ -18,7 +18,7 @@ Just pass the generated API key and Movie ID for establishing the connection. ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Google-webfonts connector and select **TMDb** from the Source type dropdown. 4. Enter your `api_key`. @@ -94,4 +94,4 @@ TMDb's [API reference](https://developers.themoviedb.org/3/getting-started/intro | Version | Date | Pull Request | Subject | | :------ | :--------- | :----------------------------------------------------- | :------------- | -| 0.1.0 | 2022-10-27 | [Init](https://github.com/airbytehq/airbyte/pull/18561)| Initial commit | \ No newline at end of file +| 0.1.0 | 2022-10-27 | [Init](https://github.com/airbytehq/airbyte/pull/18561)| Initial commit | diff --git a/docs/integrations/sources/tplcentral.md b/docs/integrations/sources/tplcentral.md index ca6a8a2a0526..092b4e2a14f7 100644 --- a/docs/integrations/sources/tplcentral.md +++ b/docs/integrations/sources/tplcentral.md @@ -4,8 +4,6 @@ The 3PL Central source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema Several output streams are available from this source: diff --git a/docs/integrations/sources/trello.md b/docs/integrations/sources/trello.md index 1626f99790a3..ebb17b4e3875 100644 --- a/docs/integrations/sources/trello.md +++ b/docs/integrations/sources/trello.md @@ -4,8 +4,6 @@ The Trello source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema Several output streams are available from this source: diff --git a/docs/integrations/sources/twilio-taskrouter.md b/docs/integrations/sources/twilio-taskrouter.md index 4c7d8b849759..5bcaca48b0c0 100644 --- a/docs/integrations/sources/twilio-taskrouter.md +++ b/docs/integrations/sources/twilio-taskrouter.md @@ -17,7 +17,7 @@ See [docs](https://www.twilio.com/docs/taskrouter/api) for more details. ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Twilio connector and select **Twilio Taskrouter** from the type dropdown. 4. Enter your `account_sid`. diff --git a/docs/integrations/sources/twilio.md b/docs/integrations/sources/twilio.md index 6cbf21a813ef..74ca262128ed 100644 --- a/docs/integrations/sources/twilio.md +++ b/docs/integrations/sources/twilio.md @@ -15,7 +15,7 @@ See [docs](https://www.twilio.com/docs/iam/api) for more details. **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Twilio connector and select **Twilio** from the type dropdown. 4. Enter your `account_sid`. diff --git a/docs/integrations/sources/tyntec-sms.md b/docs/integrations/sources/tyntec-sms.md index 7a4197c7c1ba..1bccf5fa4ab8 100644 --- a/docs/integrations/sources/tyntec-sms.md +++ b/docs/integrations/sources/tyntec-sms.md @@ -19,7 +19,7 @@ A Tyntec SMS API Key and SMS message request ID are required for this connector #### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Tyntec SMS connector and select **Tyntec SMS** from the Source type dropdown. 4. Enter your `Tyntec API Key`. @@ -62,4 +62,4 @@ The Tyntec SMS connector should not run into limitations under normal usage. Ple | Version | Date | Pull Request | Subject | |:--------|:-----------|:---------------------------------------------------------|:------------------------------------------------| -| 0.1.0 | 2022-11-02 | [18883](https://github.com/airbytehq/airbyte/pull/18883) | 🎉 New Source: Tyntec SMS | \ No newline at end of file +| 0.1.0 | 2022-11-02 | [18883](https://github.com/airbytehq/airbyte/pull/18883) | 🎉 New Source: Tyntec SMS | diff --git a/docs/integrations/sources/typeform.md b/docs/integrations/sources/typeform.md index 68bdac369223..8ba7b56579a0 100644 --- a/docs/integrations/sources/typeform.md +++ b/docs/integrations/sources/typeform.md @@ -27,7 +27,7 @@ To get the API token for your application follow this [steps](https://developer. **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Typeform** from the Source type dropdown and enter a name for this connector. 4. Fill-in 'API Token' and 'Start Date' diff --git a/docs/integrations/sources/visma-economic.md b/docs/integrations/sources/visma-economic.md index b70464ef5754..eb5f6f6369ee 100644 --- a/docs/integrations/sources/visma-economic.md +++ b/docs/integrations/sources/visma-economic.md @@ -17,7 +17,7 @@ In sort your options are: ## Set up the Visma e-conomic source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Stripe** from the Source type dropdown. 4. Enter a name for your source. @@ -51,4 +51,4 @@ For more information about the api see the [E-conomic REST API Documentation](ht | Version | Date | Pull Request | Subject | | :------ |:-----------|:----------------------------------------------------|:-----------------------------------| -| 0.1.0 | 2022-xx-xx | [18595](https://github.com/airbytehq/airbyte/pull/18595) | Adding Visma e-conomic as a source | \ No newline at end of file +| 0.1.0 | 2022-xx-xx | [18595](https://github.com/airbytehq/airbyte/pull/18595) | Adding Visma e-conomic as a source | diff --git a/docs/integrations/sources/waiteraid.md b/docs/integrations/sources/waiteraid.md index 7b0411ac7fa2..278cf94fbd63 100644 --- a/docs/integrations/sources/waiteraid.md +++ b/docs/integrations/sources/waiteraid.md @@ -11,7 +11,7 @@ You can find or create authentication tokens within [Waiteraid](https://app.wait ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Waiteraid connector and select **Waiteraid** from the Source type dropdown. 4. Enter your `auth_token` - Waiteraid Authentication Token. diff --git a/docs/integrations/sources/wikipedia-pageviews.md b/docs/integrations/sources/wikipedia-pageviews.md index 249204b28334..7a47e8d87905 100644 --- a/docs/integrations/sources/wikipedia-pageviews.md +++ b/docs/integrations/sources/wikipedia-pageviews.md @@ -12,7 +12,7 @@ None ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 **Wikipedia Pageviews** from the Source type dropdown. 4. Enter your parameters. @@ -50,4 +50,4 @@ The Wikipedia Pageviews source connector supports the following [sync modes](htt | Version | Date | Pull Request | Subject | | :------ | :--------- | :----------------------------------------------------- | :------------- | -| 0.1.0 | 2022-10-31 | [#18343](https://github.com/airbytehq/airbyte/pull/18343) | Initial commit | \ No newline at end of file +| 0.1.0 | 2022-10-31 | [#18343](https://github.com/airbytehq/airbyte/pull/18343) | Initial commit | diff --git a/docs/integrations/sources/woocommerce.md b/docs/integrations/sources/woocommerce.md index 35c9dd59c2db..45285edea041 100644 --- a/docs/integrations/sources/woocommerce.md +++ b/docs/integrations/sources/woocommerce.md @@ -24,7 +24,7 @@ You will need to generate new API key with read permissions and use `Customer ke ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 WooCommerce connector and select **WooCommerce** from the Source type dropdown. diff --git a/docs/integrations/sources/workable.md b/docs/integrations/sources/workable.md index de9267036cfa..fdcc877d8feb 100644 --- a/docs/integrations/sources/workable.md +++ b/docs/integrations/sources/workable.md @@ -12,7 +12,7 @@ You can find or create a Workable access token within the [Workable Integrations ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Workable connector and select **Workable** from the Source type dropdown. 4. Enter your `api_token` - Workable Access Token. diff --git a/docs/integrations/sources/wrike.md b/docs/integrations/sources/wrike.md index 0b2c8d49e35e..a0bce0c8e9a4 100644 --- a/docs/integrations/sources/wrike.md +++ b/docs/integrations/sources/wrike.md @@ -8,7 +8,7 @@ This page guides you through the process of setting up the Wrike source connecto ## Set up the Wrike source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte OSS account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte OSS account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Wrike** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/youtube-analytics.md b/docs/integrations/sources/youtube-analytics.md index c797d564979a..fc6af90d753e 100644 --- a/docs/integrations/sources/youtube-analytics.md +++ b/docs/integrations/sources/youtube-analytics.md @@ -22,7 +22,7 @@ Youtube also generates historical data reports covering the 30-day period prior ### For Airbyte Cloud: -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 YouTube Analytics connector and select **YouTube Analytics** from the Source type dropdown. 4. Select `Authenticate your account`. diff --git a/docs/integrations/sources/zendesk-chat.md b/docs/integrations/sources/zendesk-chat.md index 55b4fbcf6f62..449c29280a75 100644 --- a/docs/integrations/sources/zendesk-chat.md +++ b/docs/integrations/sources/zendesk-chat.md @@ -14,7 +14,7 @@ This page contains the setup guide and reference information for the Zendesk Cha **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Zendesk Chat** from the Source type dropdown. 4. Enter the name for the Zendesk Chat connector. diff --git a/docs/integrations/sources/zendesk-support.md b/docs/integrations/sources/zendesk-support.md index 8ff652a2be65..a7f71ce8ddc5 100644 --- a/docs/integrations/sources/zendesk-support.md +++ b/docs/integrations/sources/zendesk-support.md @@ -9,7 +9,7 @@ This page guides you through setting up the Zendesk Support source connector. ## Set up the Zendesk Support source connector -1. Log into your [Airbyte Cloud](https://cloud.airbyte.io/workspaces) or Airbyte Open Source account. +1. Log into your [Airbyte Cloud](https://cloud.airbyte.com/workspaces) or Airbyte Open Source account. 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Zendesk Support** from the Source type dropdown. 4. Enter a name for your source. diff --git a/docs/integrations/sources/zendesk-talk.md b/docs/integrations/sources/zendesk-talk.md index 04b76520f520..6f81a66621ee 100644 --- a/docs/integrations/sources/zendesk-talk.md +++ b/docs/integrations/sources/zendesk-talk.md @@ -21,7 +21,7 @@ Another option is to use OAuth2.0 for authentication. See [Zendesk docs](https:/ **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces) account. +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) 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 Zendesk Talk connector and select **Zendesk Talk** from the Source type dropdown. 4. Fill in the rest of the fields: diff --git a/docs/integrations/sources/zenloop.md b/docs/integrations/sources/zenloop.md index 6df789d4d55f..8cec2f08e87e 100644 --- a/docs/integrations/sources/zenloop.md +++ b/docs/integrations/sources/zenloop.md @@ -6,7 +6,7 @@ This page contains the setup guide and reference information for the Zenloop sou **For Airbyte Cloud:** -1. [Log into your Airbyte Cloud](https://cloud.airbyte.io/workspaces). +1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces). 2. Click **Sources** and then click **+ New source**. 3. On the Set up the source page, select **Zenloop** from the Source type dropdown. 4. Enter the name for the Zenloop connector. diff --git a/docs/integrations/sources/zoho-crm.md b/docs/integrations/sources/zoho-crm.md index cda2cc5b29b6..9b5bf8472eb0 100644 --- a/docs/integrations/sources/zoho-crm.md +++ b/docs/integrations/sources/zoho-crm.md @@ -6,8 +6,6 @@ The Zoho CRM source supports both Full Refresh and Incremental syncs. You can ch Airbyte uses [REST API](https://www.zoho.com/crm/developer/docs/api/v2/modules-api.html) to fetch data from Zoho CRM. -This Source Connector is based on an [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema This Source is capable of syncing: diff --git a/docs/integrations/sources/zuora.md b/docs/integrations/sources/zuora.md index f78b99db7bea..a2fe0a61f435 100644 --- a/docs/integrations/sources/zuora.md +++ b/docs/integrations/sources/zuora.md @@ -6,8 +6,6 @@ The Zuora source supports both Full Refresh and Incremental syncs. You can choos Airbyte uses [REST API](https://www.zuora.com/developer/api-reference/#section/Introduction) to fetch data from Zuora. The REST API accepts [ZOQL \(Zuora Object Query Language\)](https://knowledgecenter.zuora.com/Central_Platform/Query/Export_ZOQL), a SQL-like language, to export the data. -This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/connector-development/cdk-python). - ### Output schema This Source is capable of syncing: diff --git a/docs/reference/api/README.md b/docs/reference/api/README.md index 7caedb572668..3600010fc1ef 100644 --- a/docs/reference/api/README.md +++ b/docs/reference/api/README.md @@ -1,7 +1,7 @@ # API Documentation Folder * `generated-api-html`: Plain HTML file automatically generated from the Airbyte OAS spec as part of the build. -* `api-documentation.md`: Markdown for API documentation Gitbook [page](https://docs.airbyte.io/api-documentation). +* `api-documentation.md`: Markdown for API documentation Gitbook [page](https://docs.airbyte.com/api-documentation). * `rapidoc-api-docs.html`: HTML for actual API Spec Documentation and linked to in the above Gitbook page. This is a S3 static website hosted out of the [`airbyte-public-api-docs bucket`](https://s3.console.aws.amazon.com/s3/buckets/airbyte-public-api-docs?region=us-east-2&tab=objects) with a [Cloudfront Distribution](https://console.aws.amazon.com/cloudfront/home?#distribution-settings:E35VD0IIC8YUEW) for SSL. This file points to the Airbyte OAS spec on Master and will automatically mirror spec changes.