Skip to main content
The Get Task Status endpoint lets you check the status and retrieve the output of any async task created by the LinkedIn API. All LinkedIn API endpoints are asynchronous — they return a task ID immediately, and you poll this endpoint to get results.

Endpoint

Query Parameters

string
required
The task ID returned by any LinkedIn API endpoint

Response

boolean
Whether the request was successful
string
The task ID
string
Current task status: pending or completed
object
The original input you provided when creating the task
object | null
The task result. null while status is pending, populated when completed

Status Values

Polling Pattern

Since all LinkedIn API tasks are asynchronous, you need to poll this endpoint to get results. Here is the recommended pattern:
  1. Call a LinkedIn API endpoint (e.g., fetch-profile) to create a task
  2. Receive the api_agent_task_id in the response
  3. Poll get-task-status every 5 seconds
  4. Stop polling when status is completed
  5. Read the results from task_output
We recommend polling every 5 seconds with a maximum of 30 attempts (about 2.5 minutes total). Most tasks complete well within this window.

Code Examples

Basic Polling

Polling with Bash Loop

Team Scoping

Task status queries are scoped to your team. You can only retrieve the status of tasks that were created with your API key. Attempting to check a task that belongs to a different team will return a 404 error.

Error Responses

FAQ

We recommend polling every 5 seconds. This provides a good balance between responsiveness and avoiding unnecessary requests. Most tasks complete within 10-60 seconds.
In rare cases, a task may remain in pending status if the Chrome extension is not running or encounters an issue. We recommend setting a timeout of 2-3 minutes. If a task has not completed within that window, check that the Chrome extension is active and try creating a new task.
Currently, you can only check one task at a time. If you need to monitor multiple tasks, make separate requests for each task ID.
Task records are persisted in the database. You can check the status of completed tasks at any time to re-read the output.
The task_type field in task_input indicates which endpoint created the task:

Learn More