<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: REST API Endpoint request (Thread)</title><description> Why are so many Endpoints missing in the REST API (v6.0). I would like to have the PUT endpoint in so many resources. Specialy for the Test Run Artifact. I am try to make a migration script for my test runs because of changes in the template (custom properties). But now i have to do it manually! </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/announcements/rants-raves/2714.aspx</link><item><guid isPermaLink="false">threadId=2714</guid><author>Pierre Legér (matthias.zurbruegg@gilgends.com)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">rest</category><title>REST API Endpoint request</title><description> Why are so many Endpoints missing in the REST API (v6.0). I would like to have the PUT endpoint in so many resources. Specialy for the Test Run Artifact. I am try to make a migration script for my test runs because of changes in the template (custom properties). But now i have to do it manually! </description><pubDate>Fri, 18 Nov 2022 10:49:00 -0500</pubDate><a10:updated>2026-03-25T02:25:31-04:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx</link></item><item><guid isPermaLink="false">messageId=5812</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> The UI does not generally allow updating a test run, so that PUT request is deliberately omitted.  </title><description> The UI does not generally allow updating a test run, so that PUT request is deliberately omitted.  We have PUTs for most of the core artifacts. Many of the endpoints are for adding/removing relationships so it does not make sense to have PUTs for them, only GET, POST and DELETE. </description><pubDate>Fri, 18 Nov 2022 14:24:49 -0500</pubDate><a10:updated>2022-11-18T14:24:59-05:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply5812</link></item><item><guid isPermaLink="false">messageId=5814</guid><author>Pierre Legér (matthias.zurbruegg@gilgends.com)</author><title> I dont understand, i can update/edit my test runs with the UI. I mean even bulk editing is possible</title><description> I dont understand, i can update/edit my test runs with the UI. I mean even bulk editing is possible.  Further i definitely disagree with your statement. It is almost always useful to have the possibility to edit things. Things change in a living ecosystem and you cant know every scenario of your users.  So it would be a much better solution to implement the edit function and allow users to decide which way they want to go. </description><pubDate>Tue, 22 Nov 2022 07:20:56 -0500</pubDate><a10:updated>2022-11-22T07:20:56-05:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply5814</link></item><item><guid isPermaLink="false">messageId=6613</guid><author>william shane (williamshane3627@gmail.com)</author><title> How can I use the user interface to make changes to my test runs? Im confused. I mean, its even fea</title><description> How can I use the user interface to make changes to my test runs? Im confused. I mean, its even feasible to bulk edit.It goes without saying that I disagree with what you said. Possessing the ability to make changes is almost always beneficial. A live ecosystem is always evolving, and its impossible to anticipate all of your users needs.  </description><pubDate>Wed, 21 Feb 2024 07:45:23 -0500</pubDate><a10:updated>2024-02-21T07:45:23-05:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply6613</link></item><item><guid isPermaLink="false">messageId=6655</guid><author>Russell Adams (merlemitchell6779@hotmail.com)</author><title> Inflectra focuses on ensuring the integrity of test data. Direct modifications to the user interfac</title><description> Inflectra focuses on ensuring the integrity of test data. Direct modifications to the user interface may result in omissions or errors.    tunnel rush     While you wait for live revisions, you can use the following methods to update test runs:  Edit by group: Use filters to select test runs to update, then apply changes to the entire group. API: Use Inflectras API to automatically update test runs in bulk. </description><pubDate>Tue, 16 Apr 2024 03:45:56 -0400</pubDate><a10:updated>2024-04-16T03:45:56-04:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply6655</link></item><item><guid isPermaLink="false">messageId=7237</guid><author>Elsa Mercury (elsafrommercury@gmail.com)</author><title>   russelladams  Inflectra focuses on ensuring the integrity of test data. Direct modifications to t</title><description>   russelladams  Inflectra focuses on ensuring the integrity of test data. Direct modifications to the user interface may result in omissions or errors.    302 angel number     While you wait for live revisions, you can use the following methods to update test runs:  Edit by group: Use filters to select test runs to update, then apply changes to the entire group. API: Use Inflectras API to automatically update test runs in bulk.    Youre totally right-keeping test data intact is super important, and making changes directly through the UI can sometimes lead to mistakes. While youre waiting on live updates, using filters to edit groups of test runs or tapping into Inflectras API for bulk changes is a smart way to stay on track without risking data issues. </description><pubDate>Fri, 09 May 2025 20:47:33 -0400</pubDate><a10:updated>2025-05-09T20:47:33-04:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply7237</link></item><item><guid isPermaLink="false">messageId=7581</guid><author>Maurice Decker Maurice Decker (leoblevins38@gmail.com)</author><title> This is a known limitation of the v6.0 REST API - not all resources expose full CRUD operations, an</title><description> This is a known limitation of the v6.0 REST API - not all resources expose full CRUD operations, and unfortunately some (like Test Run Artifacts) are read-only or only partially supported.  In many cases, PUT endpoints were intentionally not implemented due to backend constraints or to prevent unintended data inconsistencies. </description><pubDate>Wed, 25 Mar 2026 02:25:31 -0400</pubDate><a10:updated>2026-03-25T09:57:43-04:00</a10:updated><link>/Support/Forum/announcements/rants-raves/2714.aspx#reply7581</link></item></channel></rss>