Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.linkup.so/llms.txt

Use this file to discover all available pages before exploring further.

We’re excited to introduce the new /tasks endpoint, which allows you to run Linkup’s core endpoints in batch and asynchronously. Run any combination of /search, /fetch, and /research calls in a single batch, with the exact same parameters as their synchronous versions, at no extra cost.

​
How to Use

  1. Send a POST /tasks request with an array of { type, input } objects (up to 100 per call). The endpoint immediately returns the tasks’ identifiers, before the work is completed.
  2. Poll GET /tasks/{id} to retrieve a specific task, or GET /tasks to list all your tasks.
  3. While running, status is pending or processing. Once the task is completed, read the result in output. If failed, inspect error.
Example Request
curl
curl --request POST \
  --url https://api.linkup.so/v1/tasks \
  --header 'Authorization: Bearer {{LINKUP_API_KEY}}' \
  --header 'Content-Type: application/json' \
  --data '[
  {
    "type": "search",
    "input": {
      "q": "What is Microsoft'\''s 2024 revenue?",
      "depth": "deep",
      "outputType": "sourcedAnswer",
      "includeDomains": ["microsoft.com", "agolution.com"],
      "excludeDomains": ["wikipedia.org"]
    }
  },
  {
    "type": "fetch",
    "input": {
      "url": "https://docs.linkup.so",
      "renderJs": false,
      "includeRawHtml": false,
      "extractImages": false
    }
  },
  {
    "type": "research",
    "input": {
      "q": "What is Microsoft'\''s 2024 revenue?",
      "outputType": "sourcedAnswer",
      "includeImages": true,
      "includeDomains": ["microsoft.com", "agolution.com"],
      "excludeDomains": ["wikipedia.org"]
    }
  }
]'

​
When to Use /tasks

  • Bulk workloads — CRM enrichment, backfilling, batch research over hundreds of queries.
  • Long-running jobs — submit the request, then poll for the result instead of waiting for the response synchronously.
  • Scheduled pipelines — kick off a nightly batch, retrieve results in the morning.
For interactive, single-shot calls (chat UIs, agent steps), keep using the synchronous /search, /fetch, and /research endpoints directly.

​
Billing

Each task is billed exactly like a direct /search, /fetch, or /research call. Read the full reference: POST /tasks · GET /tasks · GET /tasks/:id.