Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Just joined slack and this may have been answered before, but can we add a `custom destination` (an API call to my internal service) for data being ingested from sources?

<@U01RQ9LJYNM> yes you can! Does <https://docs.airbyte.io/integrations/custom-connectors|https://docs.airbyte.io/integrations/custom-connectors> answer your question?

<@U01A6TEQXRU> it does! I was not sure if we can add a destination connector as well . If that is possible, then it answers my question.

<@U01RQ9LJYNM> it’s possible but not well documented as it’s not as stable as sources yet. So your use case is to push data into an internal API? can you give me an idea of what this API is so I can give some idea of how to move forward?

<@U01A6TEQXRU> its going to be a rest API that will consume datasets (files or data streams). So essentially as Airbyte ingests data, it will push to the rest API for data pipeline processing.

Got it. It’s definitely possible to do it. We are just short on docs at the moment, but I’m happy to walk you through this. The easiest way to do it would be in Java, but it’s certainly possible to do it in other languages

<@U01RQ9LJYNM> what’s your timeline for implementing it? if it’s not urgent, we can improve our current docs to make it accessible in the next few weeks. If it’s urgent, we can work on something sooner. Could you open a Github issue with this info?

Hi <@U01A6TEQXRU> we intend to do it in the next 2-3 weeks