<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Ingest data from REST endpoint into Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/ingest-data-from-rest-endpoint-into-databricks/m-p/155367#M54234</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm looking for the best option to retrieve between 1-1.5TB of data per day from a REST API into Databricks.&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Rodrigo Escamilla&lt;/P&gt;</description>
    <pubDate>Thu, 23 Apr 2026 20:10:44 GMT</pubDate>
    <dc:creator>RodrigoE</dc:creator>
    <dc:date>2026-04-23T20:10:44Z</dc:date>
    <item>
      <title>Ingest data from REST endpoint into Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/ingest-data-from-rest-endpoint-into-databricks/m-p/155367#M54234</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm looking for the best option to retrieve between 1-1.5TB of data per day from a REST API into Databricks.&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Rodrigo Escamilla&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 20:10:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/ingest-data-from-rest-endpoint-into-databricks/m-p/155367#M54234</guid>
      <dc:creator>RodrigoE</dc:creator>
      <dc:date>2026-04-23T20:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest data from REST endpoint into Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/ingest-data-from-rest-endpoint-into-databricks/m-p/155373#M54236</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/201196"&gt;@RodrigoE&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;It would be helpful to have additional information to recommend the best options for your scenario.&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Who owns the REST API?&lt;/LI&gt;
&lt;LI&gt;Is that in your control?&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Can the source push data to Databricks, or should you pull on a schedule?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If the source can push the data, consider &lt;A style="font-family: inherit; background-color: #ffffff;" href="https://www.databricks.com/blog/announcing-general-availability-zerobus-ingest-part-lakeflow-connect" target="_blank"&gt;Zerobus&lt;/A&gt;&lt;SPAN&gt;. T&lt;/SPAN&gt;&lt;SPAN&gt;his is the cleanest, most scalable Databricks-native pattern if the producer is under your control.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;If you have no control over the source, you can build a custom Python data source wrapping their REST API and run it as a Databricks job/stream. While the pattern will work for your volumes,&amp;nbsp;the bottleneck is usually the API’s own throughput/limits, not Databricks.&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Apr 2026 21:10:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/ingest-data-from-rest-endpoint-into-databricks/m-p/155373#M54236</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-04-23T21:10:08Z</dc:date>
    </item>
  </channel>
</rss>

