Static URL possible when form having minor changes?

We’re encountering a problem while trying to make a case management system consistently extract submission data from a Kobo account.

The way this is intended to work is that a web service is set up within the system which looks for a specific URL - as provided by Kobo’s APIs. This URL contains JSON data of all submissions for a form. The web service in the system accesses that URL, and converts that data into individual cases.

The problem we’re encountering is that every single time the Kobo form is updated with minor amendments such as new choices in a particular question, the form’s “number” changes. So while the web service may have previously extracted data from, it now has to look for

This means the web service’s URL source has to be changed every time an amendment is made.

Does Kobo have - or can Kobo provide - a “static” URL from which form submissions can be downloaded, which will remain the same for a particular form regardless of the deployments it undergoes, where all submissions - across all versions - can be found?

replying to myself here in case it helps someone see it. Has anyone got any advice regarding the above?

Hi @karenmcdonnellca,

We recommend you to use the KPI API and not the KoBoCAT API. If you follow this format: https://[kpi]/api/v2/assets/{asset_uid}/, {asset_uid} stays the same even after a form redeployment.