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, completed, or failed
object
The original input you provided when creating the task
object | null
The task result. null while status is pending, populated when completed
string | null
Why the task failed. Present only when status is failed, either the error the Chrome extension reported or a note that no extension picked the task up within 24 hours. Failed tasks are retryable: submit the same request again.

Status Values

There is no processing status. A task is pending until it is completed or failed.

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 or failed
  5. Read the results from task_output, or the reason from error if it failed
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.
A task stays pending while no Chrome extension has picked it up. If none does within 24 hours, the task turns failed with the reason in error. Do not wait that long in code: set a client timeout of 2 to 3 minutes, check that the extension is active, and submit the task again.
Currently, you can only check one task at a time. If you need to monitor multiple tasks, make separate requests for each task ID.
No. Task records are kept indefinitely. You can check the status of a completed task at any time to re-read its output.
The task_type field in task_input indicates which endpoint created the task:

Learn More