I am not sure if this is what you are asking, but the relationship option is for the authenticated user, whereas the other is for a selected user ID. So if you think about the browse content page, when I am logged in, I can see what I have authored, what I have participated in, and my history (recently viewed). Relationship is connected to the user authenticated in the call rather than a passed user URL.
At least this what I am reading in the definition.
Choose one of the following options:
- participated - Returns content where the authenticated user participated in
Thanks for re-reading the docs.
So there is likely no REST API for "/people/USERNAME/content?filterID=participated". I wonder about the use case but that's a different story.
I'll call /admin/user-delete.jsp to get the information.
What exactly are you trying to do? Are you just trying to determine if the user has created anything (base content or replied to any content)? Or are you also trying to get everything a user has created?
Actually I want to delete users who created no content. I don't care about likes, bookmarks or private messages.
These users may
a) be disabled, so they are safe to delete.
b) have registered and logged in at day X and never logged in again. So they shouldn't notice the deletion. Some of them are typical SEO users with a nice image, homepage link and bio. Don't ask me about the others.
The REST calls provide little information. To reduce the number of calls I think of fetching the Community Report CVS with all users - one call which returns a lot of info.
Another approach may be to utilize the DES services. You could create some filters to determine users who have logged in but never created or modified or even viewed content if you suspect there are spam accounts.
At the least this could help narrow down that list of users, then doing some other queries as Joey mentioned may pinpoint the users.
I had a conversation with Ryan Rutan about this. It looks like you have two options depending on what you are trying to do.
Use the /activities endpoint and filter by author:
or use the RunAs feature and pass the user ID in the header:
This way you can use the relationship filter because you are now impersonating the user.