<?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 API response code when running a new job in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/api-response-code-when-running-a-new-job/m-p/124018#M47113</link>
    <description>&lt;P&gt;We are attempting to use the &lt;STRONG&gt;POST /api/2.2/jobs/run-now&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;endpoint using oAuth 2.0 Client Credentials authentication.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We are finding that when sending a request with an expired token, we receive a HTTP code of 400. This contradicts the documentation on these codes, see link below. When sending an invalid token format we receive 401, however when sending a valid format but expired token, we receive a 400. According to the documentation we'd expect this to be the other way around.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.databricks.com/api/workspace/jobs/runnow" target="_blank" rel="noopener"&gt;https://docs.databricks.com/api/workspace/jobs/runnow&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This is critical for us because the platform we use to connect (Appian) required a 401 response in order to request a new token.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Jul 2025 11:00:59 GMT</pubDate>
    <dc:creator>glevin1</dc:creator>
    <dc:date>2025-07-04T11:00:59Z</dc:date>
    <item>
      <title>API response code when running a new job</title>
      <link>https://community.databricks.com/t5/data-engineering/api-response-code-when-running-a-new-job/m-p/124018#M47113</link>
      <description>&lt;P&gt;We are attempting to use the &lt;STRONG&gt;POST /api/2.2/jobs/run-now&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;endpoint using oAuth 2.0 Client Credentials authentication.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We are finding that when sending a request with an expired token, we receive a HTTP code of 400. This contradicts the documentation on these codes, see link below. When sending an invalid token format we receive 401, however when sending a valid format but expired token, we receive a 400. According to the documentation we'd expect this to be the other way around.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.databricks.com/api/workspace/jobs/runnow" target="_blank" rel="noopener"&gt;https://docs.databricks.com/api/workspace/jobs/runnow&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This is critical for us because the platform we use to connect (Appian) required a 401 response in order to request a new token.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 11:00:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/api-response-code-when-running-a-new-job/m-p/124018#M47113</guid>
      <dc:creator>glevin1</dc:creator>
      <dc:date>2025-07-04T11:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: API response code when running a new job</title>
      <link>https://community.databricks.com/t5/data-engineering/api-response-code-when-running-a-new-job/m-p/124985#M47308</link>
      <description>&lt;P&gt;Hello gelvin&lt;BR /&gt;&lt;SPAN&gt;Please raise the ticket using this lik&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://help.databricks.com/s/contact-us?ReqType=training" target="_blank" rel="nofollow noopener noreferrer"&gt;https://help.databricks.com/s/contact-us?ReqType=training&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;Please explain the issue clearly so that it will be easy for supoort team to help easily.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 22:32:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/api-response-code-when-running-a-new-job/m-p/124985#M47308</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-11T22:32:08Z</dc:date>
    </item>
  </channel>
</rss>

