Skip to main content
POST
https://api.linkupapi.com
/
v1
/
posts
/
time-spent
Send Post Time Spent Signal
curl --request POST \
  --url https://api.linkupapi.com/v1/posts/time-spent \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '
{
  "post_url": "<string>",
  "duration": 123,
  "duration_start_time": 123,
  "login_token": "<string>",
  "country": "<string>"
}
'
{
  "status": "success",
  "message": "Time spent signal sent successfully"
}
Send a time spent signal to LinkedIn indicating how long a user spent viewing a specific post. This helps with engagement tracking and analytics.
This endpoint costs 1 credit per request.

​
Header Parameters

​
x-api-key
string
required
Your API key

​
Body Parameters

​
post_url
string
required
URL of the LinkedIn post to send time spent signal for
​
duration
integer
required
Duration in milliseconds that the user spent viewing the post. Must be a positive integer.
​
duration_start_time
integer
Optional start time in milliseconds when the user began viewing the post
​
login_token
string
required
LinkedIn authentication cookie obtained from the login/verify process
​
country
string
default:"FR"
Country code for proxy selection. Available: (US, UK, FR, DE, NL, IT, IL, CA, BR, ES, IN)

​
Response

​
status
string
Request status (success/error)
​
message
string
Detailed status message about the time spent signal request
{
  "status": "success",
  "message": "Time spent signal sent successfully"
}

​
Notes

​
Duration Requirements

  • Duration must be provided in milliseconds
  • Must be a positive integer value
  • Represents the actual time spent viewing the post

​
Optional Parameters

  • duration_start_time: Can be used to specify when the viewing session began
  • If provided, must be an integer in milliseconds

​
Post URL Support

  • Supports multiple LinkedIn post URL formats
  • Must be a valid LinkedIn post that is accessible with the provided login token
  • The API automatically extracts the activity ID from the URL

​
Error Handling

  • Invalid Cookie: Returned when the login token is expired or invalid
  • Invalid Post URL: Returned when the post URL format is incorrect or the activity ID cannot be extracted
  • Invalid Parameters: Returned when required parameters are missing or have invalid values
  • Insufficient Credits: Returned when the API key doesn’t have enough credits

​
Engagement Tracking

  • Signals are sent to LinkedIn’s analytics system
  • The signal is associated with the user identity from the login token

​
Rate Limits

  • Consider implementing appropriate delays between requests