<?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 Does using SDK API calls cost money? in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/does-using-sdk-api-calls-cost-money/m-p/114636#M3213</link>
    <description>&lt;P&gt;When using the Databricks SDK to retrieve metadata—such as catalogs, schemas, or tables—through its built-in API endpoints, does this incur any cost similar to running SQL queries?&lt;/P&gt;&lt;P&gt;Specifically, executing SQL queries via the API spins up a compute cluster (such as a SQL warehouse), which results in usage-based charges. The question is whether accessing metadata through the SDK's native endpoints also triggers compute resources in the same way, or if it avoids those costs entirely. How the native endpoints actually work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 06 Apr 2025 16:02:50 GMT</pubDate>
    <dc:creator>Skully</dc:creator>
    <dc:date>2025-04-06T16:02:50Z</dc:date>
    <item>
      <title>Does using SDK API calls cost money?</title>
      <link>https://community.databricks.com/t5/administration-architecture/does-using-sdk-api-calls-cost-money/m-p/114636#M3213</link>
      <description>&lt;P&gt;When using the Databricks SDK to retrieve metadata—such as catalogs, schemas, or tables—through its built-in API endpoints, does this incur any cost similar to running SQL queries?&lt;/P&gt;&lt;P&gt;Specifically, executing SQL queries via the API spins up a compute cluster (such as a SQL warehouse), which results in usage-based charges. The question is whether accessing metadata through the SDK's native endpoints also triggers compute resources in the same way, or if it avoids those costs entirely. How the native endpoints actually work?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 06 Apr 2025 16:02:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/does-using-sdk-api-calls-cost-money/m-p/114636#M3213</guid>
      <dc:creator>Skully</dc:creator>
      <dc:date>2025-04-06T16:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: Does using SDK API calls cost money?</title>
      <link>https://community.databricks.com/t5/administration-architecture/does-using-sdk-api-calls-cost-money/m-p/114685#M3215</link>
      <description>&lt;P&gt;Hi there&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/133101"&gt;@Skully&lt;/a&gt;, You are right since you are just fetching the metadata information from catalog, tables etc instead of directly interacting or running any SQL queries, it doesn't cost same as creating a compute.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;when we retrieve the metadata information like catalog, info , tables etc the endpoint makes API calls to the compute pane getting info from the metastore instead of create an SQL warehouse. Hence cost is different(quite low or none). You can get more info about this by looking into the unity catalog docs.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2025 06:55:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/does-using-sdk-api-calls-cost-money/m-p/114685#M3215</guid>
      <dc:creator>ashraf1395</dc:creator>
      <dc:date>2025-04-07T06:55:52Z</dc:date>
    </item>
  </channel>
</rss>

