The LinkedIn source collects LinkedIn content by keyword or user as part of a Data Stream.
Datastreamer selects from available providers automatically based on your Job configuration. You do not need to manage provider accounts or credentials to use this source.
API data_source: linkedin_auto
Configuring a Job
The query type decides how a LinkedIn Job searches: across the whole platform or from one account. Each Job uses one query type, set in query.query_type (the Query Type field on the Portal's New Job form), with query.platform set to linkedin. To cover more than one, create a Job for each.
- Search by topic.
keywordfinds posts that mention your terms anywhere on LinkedIn. - Follow an account.
userandcompanycollect posts from one user or company page.
Query types
| Query Type (Portal) | query_type | Fields | Notes |
|---|---|---|---|
| Posts by keyword | keyword | query | Keyword to search for in posts. AND, OR and NOT are supported; broader or more complex queries may return older results. |
| Posts by user | user | query | The LinkedIn user ID. |
| Posts by company | company | query | The LinkedIn company ID. |
The query object for each type:
{"platform": "linkedin", "query_type": "keyword", "query": "electric vehicles"}
{"platform": "linkedin", "query_type": "user", "query": "williamhgates"}
{"platform": "linkedin", "query_type": "company", "query": "datastreamer"}Job options
| Field | Description |
|---|---|
query.prioritization | freshness favors newer documents; coverage favors collecting a greater volume. See Freshness or Coverage. |
job_type | onetime runs once over a date range; periodic runs on a schedule. |
query_from, query_to | One-time Jobs only. Optional start and end of the date range, in ISO 8601 format. |
max_documents | Optional. Maximum documents to return. This is a soft limit: because pipelines are asynchronous, a few more documents may be returned. |
query.max_excess_documents | Optional. When filtering by date, the maximum number of documents outside the date range to process before stopping. A cost control: retrieved documents are billed even when they are discarded. |
label, tags | Optional. A label for grouping Jobs, and tags for filtering. |
Example Job request
curl --request POST \
--url 'https://api.platform.datastreamer.io/api/pipelines/{PIPELINE_ID}/components/{COMPONENT_ID}/jobs?ready=true' \
--header 'apikey: <your-api-key>' \
--header 'Content-Type: application/json' \
--data '{
"job_name": "linkedin-example",
"component_name": "linkedin-auto",
"query": {
"platform": "linkedin",
"query_type": "company",
"query": "datastreamer",
"prioritization": "coverage"
},
"data_source": "linkedin_auto",
"job_type": "onetime",
"query_from": "2026-10-01T00:00:00Z",
"query_to": "2026-10-02T00:00:00Z",
"max_documents": 1000
}'Refer to the Job creation documentation for full configuration details: Creating Jobs
API Reference: Create a Job
What is Collected
Each document returned from the LinkedIn source is mapped to the Datastreamer Unify Schema. Comments are not collected from LinkedIn. Profile details require an enrichment step. See the Schema Reference for field details, and the Data Stream Sources Capability Table for per-source capabilities.
Troubleshooting
Job fails or returns no data
- Verify your requirements are not too restrictive (they may exclude all providers)
- Check that the date period contains available data
- Review Job logs for specific errors
Unexpectedly high document counts
- Review the number of documents collected in your Job
- Set a document limit on the Job
- Review the DVU pricing page
Provider switch noted in Job logs
- This is expected behavior. If a provider is unavailable, the Job is routed to an alternative automatically. No action is required.
Related
- Sources Overview
- Creating Jobs
- Data Volume Units
- Direct Integrations: use if you need a specific provider directly
Updated 14 days ago
