Recently Oengus.io added a basic "custom data" field for each run on a schedule, it's just a basic text field though. My basic idea is to enforce a JSON object as a string for our use and just map that over to our already existent custom data system.
Recently Oengus.io added a basic "custom data" field for each run on a schedule, it's just a basic text field though. My basic idea is to enforce a JSON object as a string for our use and just map that over to our already existent custom data system.
There's some documentation that may be helpful at https://docs.oengus.io/#operation/findAllForMarathonUsingGET_1