Hello,
Do you have option to get posts created by me?
Or posts that I Like?
Or posts that created by users I’m following?
Thanks
I guess it depends which sdk and plattform you are using.
I am working with the ts-sdk and there seems to be no option for advanced queries other than this beta feature which is not part of the sdk yet Content Search - Amity Docs
I’m working with Flutter SDK
Hello, are you referring to query posts? if yes, please refer to this section: Query Post - Amity Docs
You can specify targetId and targetType - currently, these are the only available options for query post via our sdk
Hi @SocialPlus_Support ,
Is there a way to query posts created by a specific user (by userId), including both posts they posted in communities and posts on their personal wall? I’ve searched through the documentation but haven’t found a method to achieve this.
Looking forward to your support.
Hello @duongnb , Yes, you can use the Search Posts API and filter by createdBy with the userId to fetch all posts by that user — including both community posts and personal wall posts.
Ref: Search Posts API docs 
1 Like
Thank you for your instructions. I’ve implemented them, but the API call is still quite slow—it takes several seconds, as shown in the attached image. Is there any way to optimize this and improve the performance? @SocialPlus_Support
Hello @duongnb , Thank you for the update.
Could you please let us know which server region you’re using? Also, does this slowness happen consistently with every request, or only occasionally?
As this feature is still in beta, we truly appreciate your feedback and will use this information to help improve performance in future updates.
Hi @SocialPlus_Support , We are currently using the SG server region. The latency frequently exceeds 1 second and occasionally takes several seconds, as previously demonstrated. In comparison to other APIs, which usually respond within 100–300 ms, this performance is considerably slower.
Hello @duongnb, Thank you for your message.
Please note that our system implements a caching mechanism, which may cause the initial data request to take slightly longer than expected. Subsequent requests should be faster as cached data is utilized.
Should the issue persist or if you observe any further irregularities, please feel free to let us know.
1 Like