Forum Discussion
6 Replies
No thank you Claudius for all the suggestions. They were definitely helpful as I learn few other things in the process.
I already got one ticket created with khoros team, waiting for the solution from them.Thanks,
Aishwarya
Thanks for trying and sorry that I lead you on another dead end. I think it was worth trying. Looks like we need some input from the folks that built this API.
Tried this as well, not working for me.
Thanks,Aishwarya
The URL parameter name in 2.0 is fields. So did you try replacing "action.key" (which should only be the name of the returned export column) by that, e.g.
website_name/t5/s/api/2.1/analytics/bulk/export?fields=kudos.give&bda.fromDate=2024-12-13T01:00&bda.toDate=2024-12-13T02:00
Thanks Claudius for the reply. I tried that way as well but its not working for me. Below are the queries which I used:
website_name/t5/s/api/2.1/analytics/bulk/export?action.key=kudos.give&bda.fromDate=2024-12-13T01:00&bda.toDate=2024-12-13T02:00
website_name/t5/s/api/2.1/analytics/bulk/export?filter[action.key]=kudos.give&bda.fromDate=2024-12-13T01:00&bda.toDate=2024-12-13T02:00
Thanks,Aishwarya
So I cannot verify myself since I don't have access to Bulk Data API v3.0 yet, but: Since Bulk Data API v3.0 is in the endpoint referred to as 2.1 I wonder if you can use the same fields parameter like in v2.0. E.g. in your example append to the API URL &fields=users.registration