@Eileenmcnaughton Yes, by all means, let's ask for the credentials. The only reason we thought Gr4vy could be in the flow was that it would be less work for FRTech but if it is easier, then let's take that approach. I will see what we need to do to get those credentials. Stay tuned.

thanks @EMartin - I'm not going to weigh in on whether involving Gravy is useful on the front end integration but on fetching data that is in there getting it directly is almost certainly less work without Gr4vy

I don't see any value @Eileenmcnaughton that Gr4vy would add other than to offload FRTech's work. I was struggling to see why we could use them other than to avoid FRTech the API integration work. If it is easier, then that settles it .

Thanks @EMartin - ignore if this is already under way, but let us know if you want us to draft the request to Chariot, or whether we'd need to log in to our instance to retrieve keys directly.

Updating here that we've looped @Eileenmcnaughton in on our email thread with Chariot regarding this. They told us that dashboard APIs are going live later this month, which is what we'll need to get the data out of Chariot into Civi. We will have to wait until then to investigate further.

Checking on this @MDemosWMF - do we need to get any documentation from Chariot at this stage?

@AKanji-WMF - no we are good - we have what we need

Thank you @Eileenmcnaughton