Hi @aaj, I just made a quick check with the REST Services on the Global Server and can confirm that itās working smoothly for me. No issues at my end. Are you on the Global Server?
Is there documentation/instructions for accessing form metadata and submission data using v2 API?
v1 API is being used in a PHP implemented REST service processing module on our server to refresh (delete and re-upload) updated csv data (media) files āattachedā to one or more kobotoolbox forms
However, switching to v2 API will require weeks, probably more, of work. v1 API (what has been used) works on xform_id, which is not available in v2. Also, the v2 asset url formats look very different from v1.
The āauto refreshā (delete and re-upload) of choices csv data files in forms is a key functionality in our implementation across all our forms. It does not work without it.
The v1 API based implementation was done over 3 years ago, and has been working smoothly up till now.
The Release 2.025.02 note states that KPI v1 endpoints are to decommissioned (is that same as deprecated?) in early 2026. So, v1 API should be available for use till then? We will then have enough time to switch our implementation to v2.
Any response/update regarding this issue, @Kal_Lam? Any idea when the v1 API (KPI v1 endpoints) will start working again? This is critical for our data collection system to work, which has been on hold for a day now.
FYI I can confirm that I can see the same behavior on Global (kc.kobotoolbox.org) v1 endpoints. Sometimes forms.json works fine, but often it seems to be failing with a 500.
Investigating.. But can you please retry a few times and see if it will (eventually) work for you too.
Thanks for the follow-up @Xiphware. I have been constantly checking forms.json since the last one and a half days (did it again just now). It has not worked for me once in that period. Curious that it works for you sometimes. I experienced that behaviour with https://kc.kobotoolbox.org/api/v1/metadata just about an hour ago. It worked a couple of times, then stopped working.
@aaj, @degami kindly please be informed that we are investigating this issue and will get back to you once we resolve it. Thank you for your kind patience and understanding!
Yep - for our Kobotoolbox-based projects weāre all in on the v2 API. But our setup back when we swapped was pretty scrappy and used for mostly small-scale projects, so it wasnāt that much work to move over.
So, the issue of v2 api request returning html instead of json has been resolved?
I have been experimenting with v2 API. Just found out that adding the query string ā?format=jsonā to the api request url, returns a json result. However ā?format=jsonā query string gets added to all the url values in the returned json result.