In Improving connections from ODK to other systems (with health focus) in Tentaive Phase 4 (September 2023 on) there is talk of implementing API Keys & webhooks.
Are these still likely or probable and on what timescale?
Many thanks
Our roadmap is at https://getodk.org/roadmap. Understanding interoperability needs is work that's coming next. Can you tell me more about your needs and the problem you are trying to solve?
Thanks for the prompt reply.
We are using ODK to do longitudinal surveys of habitats (in general ponds but also associated terrestrial habitats). We are exploring a new final repository for the data and new workflows to make the whole thing work better and make the data more accessible. The final data repository is likely to be a custom MySQL database using a C# or Python API for access. A couple of things we are thinking about:
-
It would be nice to be able to have webhooks push data into our database(on ODK record create or update), though I acknowledge that we could simply poll ODK central for changes but the webhook approach seems nicer. In our case the data transfer is not time critical, and if a webhook fails it would not be a disaster. Being able to force firing of a webhook manually would be important to enable us to sort failed webhooks easily
-
It might be that we provide a way of editing entities via the API. An API key seems a much better approach than a user/password
-
On another matter SSO that can work with Entra ID (Azure AD) or Google would be great
M
1 Like