Skip to main content
POST
Get Conversation Messages
Get detailed messages from a LinkedIn conversation using either a LinkedIn profile URL or a direct conversation ID, including message content, timestamps, and sender information.
Credit Usage: 1 credit per 10 results (or fraction thereof). For example:
  • 1-10 results = 1 credit
  • 11-20 results = 2 credits
  • 300 results = 30 credits

Header Parameters

string
required
Your API key

Body Parameters

string
URL of the LinkedIn profile to get conversation messages with. Required if conversation_id is not provided.
string
Direct conversation ID to retrieve messages from. Required if linkedin_url is not provided.
integer
default:"10"
Number of messages per page
string
Timestamp of the last message for pagination. Omit for the first request to get the most recent messages.
string
default:"FR"
Country code for proxy selection. Available: US, CA, MX, CR, BR, AR, CL, CO, FR, UK, DE, NL, ES, IT, PT, BE, CH, AT, IE, SE, DK, FI, LT, LV, EE, PL, CZ, SK, HU, RO, UA, SI, HR, RS, AL, GR, CY, TR, IL, AE, EG, ZA, IN, PK, BD, JP, SG, MY, ID, TH, PH, AU
string
required
LinkedIn authentication cookie obtained from the login/verify process

Response

string
Request status (success/error)
object

Notes

  • Two Access Methods: You can retrieve conversation messages using either:
    • LinkedIn Profile URL: The API will first find the conversation ID associated with that profile
    • Direct Conversation ID: Skip the profile lookup and access the conversation directly
  • Parameter Requirements: Either linkedin_url OR conversation_id must be provided (not both required)
  • Messages are returned in chronological order (most recent first)
  • The timestamp is in milliseconds since epoch
  • Cursor-based Pagination:
    • First request: Omit the cursor parameter to get the most recent messages
    • Subsequent requests: Pass the next_cursor value from the previous response as the cursor parameter
    • End of results: When has_next_page is false, there are no more messages to fetch
    • Use total_results to control how many messages are returned per request (default: 10)
  • When using linkedin_url, the API first retrieves the conversation ID for the specified profile, then fetches the messages
  • When using conversation_id, the API directly fetches messages from that conversation
  • This endpoint can only retrieve messages with profiles you’ve already had a conversation with
  • Historical messages may be limited by LinkedIn’s data retention policies
  • The profile_url field is only included in the response when it was provided in the request

Pagination Example