<?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>article Synthetic Monitoring: How to Convert Location IDs Between HTTP Monitors execution API and the Locations API in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Monitoring-How-to-Convert-Location-IDs-Between-HTTP/ta-p/295123</link>
    <description>&lt;H2&gt;&lt;STRONG&gt;Summary&lt;/STRONG&gt;&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;When working with the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/STRONG&gt;&lt;/A&gt; and the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic locations API v2&lt;/STRONG&gt;&lt;/A&gt;, you may notice that &lt;STRONG&gt;location IDs&lt;/STRONG&gt; don’t match.&lt;BR /&gt;This happens because:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The &lt;STRONG&gt;HTTP Monitor executions API&lt;/STRONG&gt; returns location IDs &lt;STRONG&gt;in decimal&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The &lt;STRONG&gt;Locations API&lt;/STRONG&gt; uses &lt;STRONG&gt;hexadecimal&lt;/STRONG&gt; location IDs&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;To query location details using the ID from a monitor execution, you must convert the decimal ID → hexadecimal and prepend the required prefix.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Example:&lt;BR /&gt;&lt;CODE&gt;54&lt;/CODE&gt; (decimal) → &lt;CODE&gt;34&lt;/CODE&gt; (hex) → &lt;CODE&gt;SYNTHETIC_LOCATION-0000000000000034&lt;/CODE&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-TOC indent="15" liststyle="disc" maxheadinglevel="3"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;
&lt;H2&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;When retrieving execution details from&amp;nbsp;the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/STRONG&gt;&lt;/A&gt;, the &lt;CODE&gt;locationId&lt;/CODE&gt; field appears in &lt;STRONG&gt;decimal format&lt;/STRONG&gt;, but when calling&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;Synthetic locations API v2 - GET a location,&lt;/A&gt; the API expects a &lt;STRONG&gt;hexadecimal location ID&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;This mismatch means that direct lookups are not possible unless the values are converted.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H2&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/H2&gt;
&lt;H3&gt;&lt;STRONG&gt;Steps&lt;/STRONG&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Retrieve the&amp;nbsp;&lt;STRONG&gt;decimal&lt;/STRONG&gt;&amp;nbsp;locationId from the HTTP Monitor execution API output&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Convert decimal → hexadecimal (any standard converter works)&lt;BR /&gt;Example:&lt;BR /&gt;&lt;CODE&gt;54 (decimal)&lt;/CODE&gt; → &lt;CODE&gt;34 (hex)&lt;/CODE&gt;&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Apply the prefix: &lt;CODE&gt;SYNTHETIC_LOCATION-00000000000000&lt;/CODE&gt;.&amp;nbsp;
&lt;OL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Apply zero-padding until the hex string is 16 characters long&lt;BR /&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Final format required by the Locations API:&lt;/DIV&gt;
&lt;PRE&gt;&lt;CODE&gt;SYNTHETIC_LOCATION-0000000000000034&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Add the location id to the Locations API call&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What's Next?&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;If this article didn’t resolve your issue, please consider &lt;STRONG&gt;opening a support ticket&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Include:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;A link to this article&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The monitor execution payload (with &lt;CODE&gt;locationId&lt;/CODE&gt;)&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The request and full response body from your Locations API call&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Any scripts or automated workflow where the mismatch occurs&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;This will help us diagnose formatting or data-transformation issues quickly.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3 class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Related reading&lt;/H3&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;Synthetic locations API v2&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426" target="_blank" rel="noopener"&gt;Synthetic Troubleshooting Map&lt;/A&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/http-monitors-classic" target="_self"&gt;HTTP Monitors (classic) documentation&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app" target="_self"&gt;Latest Dynatrace Synthetic App&lt;/A&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 24 Feb 2026 20:04:52 GMT</pubDate>
    <dc:creator>HannahM</dc:creator>
    <dc:date>2026-02-24T20:04:52Z</dc:date>
    <item>
      <title>Synthetic Monitoring: How to Convert Location IDs Between HTTP Monitors execution API and the Locations API</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Monitoring-How-to-Convert-Location-IDs-Between-HTTP/ta-p/295123</link>
      <description>&lt;H2&gt;&lt;STRONG&gt;Summary&lt;/STRONG&gt;&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;When working with the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/STRONG&gt;&lt;/A&gt; and the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic locations API v2&lt;/STRONG&gt;&lt;/A&gt;, you may notice that &lt;STRONG&gt;location IDs&lt;/STRONG&gt; don’t match.&lt;BR /&gt;This happens because:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The &lt;STRONG&gt;HTTP Monitor executions API&lt;/STRONG&gt; returns location IDs &lt;STRONG&gt;in decimal&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The &lt;STRONG&gt;Locations API&lt;/STRONG&gt; uses &lt;STRONG&gt;hexadecimal&lt;/STRONG&gt; location IDs&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;To query location details using the ID from a monitor execution, you must convert the decimal ID → hexadecimal and prepend the required prefix.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Example:&lt;BR /&gt;&lt;CODE&gt;54&lt;/CODE&gt; (decimal) → &lt;CODE&gt;34&lt;/CODE&gt; (hex) → &lt;CODE&gt;SYNTHETIC_LOCATION-0000000000000034&lt;/CODE&gt;&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;LI-TOC indent="15" liststyle="disc" maxheadinglevel="3"&gt;&lt;/LI-TOC&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;
&lt;H2&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;When retrieving execution details from&amp;nbsp;the &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/STRONG&gt;&lt;/A&gt;, the &lt;CODE&gt;locationId&lt;/CODE&gt; field appears in &lt;STRONG&gt;decimal format&lt;/STRONG&gt;, but when calling&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;Synthetic locations API v2 - GET a location,&lt;/A&gt; the API expects a &lt;STRONG&gt;hexadecimal location ID&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;This mismatch means that direct lookups are not possible unless the values are converted.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H2&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/H2&gt;
&lt;H3&gt;&lt;STRONG&gt;Steps&lt;/STRONG&gt;&lt;/H3&gt;
&lt;OL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Retrieve the&amp;nbsp;&lt;STRONG&gt;decimal&lt;/STRONG&gt;&amp;nbsp;locationId from the HTTP Monitor execution API output&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Convert decimal → hexadecimal (any standard converter works)&lt;BR /&gt;Example:&lt;BR /&gt;&lt;CODE&gt;54 (decimal)&lt;/CODE&gt; → &lt;CODE&gt;34 (hex)&lt;/CODE&gt;&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Apply the prefix: &lt;CODE&gt;SYNTHETIC_LOCATION-00000000000000&lt;/CODE&gt;.&amp;nbsp;
&lt;OL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Apply zero-padding until the hex string is 16 characters long&lt;BR /&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Final format required by the Locations API:&lt;/DIV&gt;
&lt;PRE&gt;&lt;CODE&gt;SYNTHETIC_LOCATION-0000000000000034&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Add the location id to the Locations API call&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What's Next?&lt;/H2&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;If this article didn’t resolve your issue, please consider &lt;STRONG&gt;opening a support ticket&lt;/STRONG&gt;.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Include:&lt;/DIV&gt;
&lt;UL&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;A link to this article&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The monitor execution payload (with &lt;CODE&gt;locationId&lt;/CODE&gt;)&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;The request and full response body from your Locations API call&lt;/LI&gt;
&lt;LI class="___ccc16d0 fje8fi8 f1ng9h0j f1bwykku f18jd3zf"&gt;Any scripts or automated workflow where the mismatch occurs&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;This will help us diagnose formatting or data-transformation issues quickly.&lt;/DIV&gt;
&lt;DIV class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3 class="paragraph-in-scc-markdown-text ___1ngh792 ftgm304 f1iaxwol"&gt;Related reading&lt;/H3&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-monitor-execution/get-http-monitor" target="_blank" rel="noopener"&gt;Synthetic monitor executions API v2 - GET HTTP monitor&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location" target="_blank" rel="noopener"&gt;Synthetic locations API v2&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;A id="link_6" class="page-link lia-link-navigation lia-custom-event" href="https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Troubleshooting-Map/ta-p/250426" target="_blank" rel="noopener"&gt;Synthetic Troubleshooting Map&lt;/A&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/http-monitors-classic" target="_self"&gt;HTTP Monitors (classic) documentation&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":open_book:"&gt;📖&lt;/span&gt;&amp;nbsp; &lt;A href="https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-on-grail/synthetic-app" target="_self"&gt;Latest Dynatrace Synthetic App&lt;/A&gt;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 24 Feb 2026 20:04:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Synthetic-Monitoring-How-to-Convert-Location-IDs-Between-HTTP/ta-p/295123</guid>
      <dc:creator>HannahM</dc:creator>
      <dc:date>2026-02-24T20:04:52Z</dc:date>
    </item>
  </channel>
</rss>

