Hello everyone,
This is a reminder that as previously mentioned, all v1 API endpoints will be permanently removed on June 2, 2026
What you need to do: If your integrations currently use v1 endpoints, you must migrate to v2 before the deadline to avoid service disruptions.
Need help? See the detailed migration article available on our support site.
We strongly encourage you to complete this transition to the more robust v2 API as soon as possible. Thank you.
@ambassadors for your reference and sharing.
I now have a clear direction, thanks to you. Mission accomplished! Seriously, thank you
Hello everyone,
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.
Thanks Team for the updates and the work done,
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 can replace it with /api/v1/submissions to /submission/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).
Hope that helps.
Hi @ignacio_gr thanks for the guidance. I will check out the Open Rosa API
Does this affect those using PowerBI and connecting to KoboToolbox ?
Hi @IAR , yes this will also affect the synchronous exports and therefore the connection with PowerBI. You should now use:
https://[server_url]/api/v2/assets/[project_asset_uid]/export-settings/
You can read more about this in these articles:
Hope that helps!
“How do I know that I have been transferred from V1 to V2?”
@Mohamedjaber1991 I believe both API are available at the moment. Users are being encouraged to move to v2, because v1 is going to be disabled soon.
@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.
Thanks @ignacio_gr I had a look. We’re already using v2 in PowerBI.
Key indicators:
assets/{uid}/submissions/akUn4Ma7a7aVs69dQZdKZBXm (not numeric ID)Sorry, these are not indicative of the v2 API. Please change /assets/{uid}/submissions/ to /api/v2/assets/{uid}/data/. The response will be identical with the exception of pagination; please see https://support.kobotoolbox.org/migrating_api.html#data-endpoints-submission-data for details. @IAR
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?
Thank you very much in advance.
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.
Hope that helps!
Thank you so very much. This is very helpful!
Hi @jnm
Thanks for replying.
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.
