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
When creating a Job for the LinkedIn source, you define what content to collect. Common configuration options include:
- Keywords / query: terms to search for across LinkedIn.
AND,ORandNOTare supported; broader or more complex queries may return older results. - User targets: specific accounts to monitor
- Date range: LinkedIn uses predefined periods (day, week or month) rather than a custom date range
- Sorting: Top or Latest
- Document limit: maximum number of documents per Job run
Refer to the Job creation documentation for full configuration details: Creating Jobs
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",
"data_source": "linkedin_auto",
"query": { "query": "electric vehicles" },
"job_type": "onetime",
"query_from": "2026-10-01T00:00:00Z",
"query_to": "2026-10-02T00:00:00Z",
"max_documents": 1000
}'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 43 minutes ago
