<?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 Re: vManage API /attachfeature returns HTTP 400 – Unable to update device template variables in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421601#M3533</link>
    <description>&lt;P&gt;Good luck.&lt;BR /&gt;If you don't get an answer there, ping me here with a link to the post there, and I'll reach out to the relevant people.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Nov 2025 23:03:18 GMT</pubDate>
    <dc:creator>obrigg</dc:creator>
    <dc:date>2025-11-05T23:03:18Z</dc:date>
    <item>
      <title>vManage API /attachfeature returns HTTP 400 – Unable to update device template variables</title>
      <link>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421598#M3530</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I’m encountering an issue when trying to update device template variables via the vManage REST API.&lt;BR /&gt;The API consistently returns an HTTP 400 Bad Request, even though the workflow follows Cisco’s documented process and mirrors the web UI “Change Device Values” operation.&lt;/P&gt;&lt;P&gt;Our goal is to automate template variable updates that are currently performed manually in the UI.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Workflow Attempted&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;&lt;STRONG&gt;Step 1 – Authentication&lt;/STRONG&gt;&lt;BR /&gt;POST /j_security_check and GET /dataservice/client/token → &lt;SPAN class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step 2 – Retrieve Device Info&lt;/STRONG&gt;&lt;BR /&gt;GET /dataservice/device → &lt;SPAN class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step 3 – Get Template Info&lt;/STRONG&gt;&lt;BR /&gt;GET /dataservice/template/device/config/attached/{templateId} → &lt;SPAN class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step 4 – Get Current Variables&lt;/STRONG&gt;&lt;BR /&gt;POST /dataservice/template/device/config/input → &lt;SPAN class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt;&lt;/SPAN&gt; retrieved full variable list&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Step 5 – Update Variables ( Failing )&lt;/STRONG&gt;&lt;BR /&gt;POST /dataservice/template/device/config/attachfeature → &lt;SPAN class="lia-unicode-emoji" title=":cross_mark:"&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt;&lt;/SPAN&gt; HTTP 400 Bad Request&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;What I’ve Tried&lt;/STRONG&gt;&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Verified isEdited = true&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Confirmed variable names match template fields&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Ensured values are string type&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Compared structure with working iTest automation payloads&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Rechecked JSON against API documentation&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;STRONG&gt;Questions&lt;/STRONG&gt;&lt;/H3&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Is the payload for /attachfeature missing any required fields or structure?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;How can I get detailed error information for 400 responses?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is this the right endpoint, or should a detach/attach sequence be used?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Does the web UI trigger additional backend calls that need to be replicated?&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 05 Nov 2025 22:52:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421598#M3530</guid>
      <dc:creator>Moxa</dc:creator>
      <dc:date>2025-11-05T22:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: vManage API /attachfeature returns HTTP 400 – Unable to update device template variables</title>
      <link>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421599#M3531</link>
      <description>&lt;P&gt;I love the fact this community draws questions outside of the Meraki space.&lt;BR /&gt;That said, in the &lt;A href="https://community.cisco.com/t5/sd-wan-and-cloud-networking/bd-p/discussions-sd-wan" target="_blank" rel="noopener nofollow noreferrer"&gt;Catalyst SD-WAN community&lt;/A&gt; you are more likely to find relevant experts who can help with vManage APIs.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 22:58:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421599#M3531</guid>
      <dc:creator>obrigg</dc:creator>
      <dc:date>2025-11-05T22:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: vManage API /attachfeature returns HTTP 400 – Unable to update device template variables</title>
      <link>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421600#M3532</link>
      <description>&lt;P&gt;Hi Oren, thanks for pointing that out, I wasn’t aware of the separate Catalyst SD-WAN space. Appreciate you guiding me to the right place!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 23:01:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421600#M3532</guid>
      <dc:creator>Moxa</dc:creator>
      <dc:date>2025-11-05T23:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: vManage API /attachfeature returns HTTP 400 – Unable to update device template variables</title>
      <link>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421601#M3533</link>
      <description>&lt;P&gt;Good luck.&lt;BR /&gt;If you don't get an answer there, ping me here with a link to the post there, and I'll reach out to the relevant people.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 23:03:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/vmanage-api-attachfeature-returns-http-400-unable-to-update/m-p/5421601#M3533</guid>
      <dc:creator>obrigg</dc:creator>
      <dc:date>2025-11-05T23:03:18Z</dc:date>
    </item>
  </channel>
</rss>

