provider slug you send to /v1/extract (e.g. the profile.info in apify/linkedin/profile.info). It specifies what data to extract.
Query-driven services (currently
place.search on Google Maps) live on the POST /v1/search endpoint instead. The slug grammar is identical; only the endpoint and the type segment differ.Available types
Search-style types (used with
POST /v1/search):
Platform coverage
Not every type is available on every platform, and coverage grows as new providers are added. Rather than baking a matrix here that drifts, query the live catalogue:supported_platforms, supported_types, and supported_search_types. The browsable list with copy-ready slugs is at socialrouter.io/providers.
Normalized response
Regardless of the provider, every extraction record includes at minimum:reaction_type for post.likes, experience and education arrays for profile.info).