To ensure a smooth transition and avoid any service disruptions, we have decided to extend the deadline of the v1 deprecation to June 2nd, 2026.
We want to ensure there is ample time for all users still using the v1 endpoints to update their integrations to v2. If this is your case, we encourage you to complete this transition as soon as possible.
As mentioned above, you can find more information on how to do this in the dedicated support article.
I have been trying to explore if there is a submission endpoint in v2 but I have not seen one.
I have been using https://kc.kobotoolbox.org/api/v1/submissions.json in my workflows to submit data to a project and would like to transition this as well.
Would be great if someone can point me to the v2 version of this endpoint.
Hi @twesigye. Unfortunately there is no exact match to api/v1/submissions in v2 (see endpoint deprecation here). But you should still be able to use the Open Rosa API (see documentation here). I believe your script should work simply by replacing /api/v1/submissions to /submission can replace it with /api/v2/assets/{uid}/data/ . The response will be identical with the exception of pagination
You can also see all the available options for v2 in the new public API documentation: KoboToolbox Primary API (available using kf. or eu. depending on the server).
@Mohamedjaber1991 you can check the url you used for your integrations. If you see …/api/v2/… in the url, it means you’re using the correct API. Otherwise you can switch it using the documentation we linked above.
Hello, I am a new user of the KoboToolbox. I am currently conducting a survey using the platform. Could you please explain whether this change affects my survey? If so, is there a video tutorial outlining the steps?
Hello @abdurakhmanov1986_ub. If your survey was simply created using the KoboToolbox interface and you have not actively used the API, this change should not affect you.
The API can be used for integrations with other tools, automated exports, or simply managing your projects without using the interface manually. You can learn more about the API in our introductory article here.
But again, in order for this update to affect your projects, you would’ve had to set up these integrations or automations yourself. Otherwise this will have no impact on your work.
I must have misread the documentation and thought I was in the clear. And I can see from your message that you strongly suggest updating the path.
At the moment my Power BI report connected directly to a KT project (which has public data) using assets/{uid}/submissions/ is still working, or so it seems (no errors on PBI service). I believe there was a hiccup a few days ago (June 02) but after that it picked up again.
A couple of weeks ago I did notice that there was a limit of 1000 records, and again not having read the documentation correctly I wasn’t aware of the next URL, but I applied a workaround to get data on a monthly basis, in a batch, and it works, because in my case, there’s never more than 1000 records in a single month.
I will look into updating the path, and report back.
I’ve noticed my PowerBI report failing for the past few days. I’ve updated it to work with API v2 and it’s working now!
Two big changes:
API v1 → v2: updated the endpoint from assets/{uid}/submissions/ to api/v2/assets/{uid}/data/
Photo URLs: extract download_url and download_small_url directly from _attachments, matching by question_xpath (previously I was constructing media urls based on “https://kc.humanitarianresponse.info/media/…” which no longer works)
One thing i’ve noticed…. I have thousands of submissions and each has at least 1 photo attached (up to 5).
When the report page loads and tries to render many thumbnails at once, some dont display at all and if I click to open the original image I get this message:
You or something on your network is sending too many requests to this service. Please wait several minutes and then try again. If you need assistance, please visit https://community.kobotoolbox.org/.
The images eventually load fine after a refresh or a short wait, so it’s clearly a rate limiting issue, just temporary.
My question: is there any documented threshold for media/attachment requests? Requests per second, per minute, per session? I couldn’t find anything in the official docs or here in the forum.