🚀 KoboToolbox Adaptor Updated for API Pagination Changes (v4.2.9+)

Adaptors & Templates
1

Hey OpenFn community,

We’re excited to announce that the KoboToolbox adaptor has been updated to handle upcoming changes to the KoboToolbox /api/v2/assets/{uid_asset}/data API endpoint.

What’s changing?

Starting with the first January 2026 release (week of January 12), KoboToolbox is implementing new pagination limits for their data API:

  • Maximum results per page: 1,000 records (down from 30,000)
  • Default results per page: 100 records (down from 30,000)

This change improves platform performance and stability as KoboToolbox scales, but it requires updated handling of paginated responses.

What we’ve done

As of version 4.2.9, the KoboToolbox adaptor automatically handles these new pagination requirements. The adaptor now:

  • Respects the new 1,000 record limit per page
  • Automatically follows next links to retrieve complete datasets
  • Maintains backward compatibility with existing workflows

What you need to do

If you’re using the KoboToolbox adaptor in your workflows:

  1. Update your adaptor version to 4.2.9 or higher before January 12, 2026
  2. Review any workflows that fetch large datasets from KoboToolbox
  3. Test your workflows to ensure they handle pagination correctly

Note: This change only affects the /data API endpoint. KoboToolbox’s synchronous export endpoints (.xlsx and .csv exports) continue to work exactly as before.

Need help?

Have you updated your workflows yet? Any questions about how this affects your integration? Drop a comment below!

2

If you’re batching downstream (like pushing into dhis2 or salesforce), the new 1k page size can actually help things go more smoothly by reducing timeouts and retries. I upgraded to 4.2.9 last week and didn’t have to do anything with my jobs. The adaptor’s next handling did all the work. It’s worth testing early if your workflows expect big single pulls, though.

1 Like
3

That’s wonderful feedback @Carole12, thank you!