transactionId filter does not have any effect on activity endpoint response
While trying to get the activity feed for a push notification, using the respective api (/v1/activity), I noticed that the query param "transactionId" that is mentioned in the documentation doesn't apply any filtering and I'm just getting the whole feed. I couldn't find an issue related to that. Is this something known or am I missing something?
URL example: v1/activity?transactionId=ca443bdc-8aaa-4144-80fb-a3ffd0a32633
Thanks!
4 Replies
@serafeimo hey, from what I see in the code for the
activity endpoint, it's not applied to any logic, I'm not sure if it's done by mistake or was on the purpose.
hmm, could you try the same request but to the /notifications endpoint instead?It seems that "/notifications?transactionId=abc" works fine. Interesting.
Thank you both! I'll test it further 🙂
yeah, the thing is that at the beginning we have had
/activity endpoint and then decided to introduce the /notifications but that one was left to support old customers, but it should be deprecated IMO
if anything let us know 😉Great, thanks again!