You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I was going through the network tab and the following endpoint for inbox https://www.linkedin.com/voyager/api/voyagerMessagingGraphQL/graphql
queryId: messengerConversations.8656fb361a8ad0c178e8d3ff1a84ce26
variables: (query:(predicateUnions:List((conversationCategoryPredicate:(category:PRIMARY_INBOX)))),count:20,mailboxUrn:{ProfileURN},lastUpdatedBefore:1736674879969)
Returns the data in following format:-
data:{
_recipeType
_type
messengerConversationsByCategoryQuery: {
_recipeType
_type
metadata
elements:[array of objects]
}
}
The objects in elements array has a parameter of "read" which is boolean. If the "read" parameter is false that means the message is unread. Can be integrated I guess.
@dreamflasher @tbressers @mekahell @kjoconnor @tomquirk
![Image](https://private-user-images.githubusercontent.com/89261520/408798369-79e22d7f-edfb-4a95-8a3d-6f5c6f27c262.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxMTgzNDgsIm5iZiI6MTczOTExODA0OCwicGF0aCI6Ii84OTI2MTUyMC80MDg3OTgzNjktNzllMjJkN2YtZWRmYi00YTk1LThhM2QtNmY1YzZmMjdjMjYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDE2MjA0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM3NDI1OGM2M2NjZjIxMzU4NTY3MDliZmZlN2JjYjgyODVlNTk4Y2M4MDc4NWE5MWMyZTJjZjNiOWJkZDhhMWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.rSjZReg398vMsSC8tnVMMKut-Gy09R8DIpPO9oSR_UE)
is there an api call to fetch only unread conversations like in the image that i have attached?
also does .get_conversations() fetch only first 20 or all? is there a way to fetch is based on pagination?
im trying to build a linkedin ai agent which manages inbox automatically based on knowledge base ingestion
The text was updated successfully, but these errors were encountered: