Documentation Index
Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Playbook
Use Apify when you need controlled web automation/scraping workflows.- Use
apify_list_store_actorsfirst when you do not know the actor id yet. - Results are ranked by quality score by default. The top result is the most reliable actor based on rating, review count, total runs, and 30-day success rate. Pick the #1 result unless you have a specific reason not to.
- Each actor in the response includes
_qualityScore(higher is better),_baseQualityScore, and_successRate30d(percentage). Prefer actors with_deeplineVetted: true, high usage/rating, and_successRate30d >= 95%. - For generic LinkedIn post scraping, prefer
supreme_coder/linkedin-post. For LinkedIn post engagers/reactions, preferharvestapi/linkedin-post-reactions. Avoid actors returned with_deeplineDownranked: trueunless the user explicitly asked for that actor. - Build
actorIdasusername/namefrom store results. - Use
apify_get_actor_input_schemato inspect required/optional fields before running. - Wrapper-level fields (
actorId,input,params,timeoutMs) and runtime validation behavior can differ from actor-page docs. - Prefer
apify_run_actor_syncas the default execution path when you want results in one call. - Use
apify_run_actoronly when you need non-blocking execution, then poll run status before fetching outputs. - Validate payload shape with a tiny run before scaling row counts.
Quality ranking
Actors are ranked by:rankBy: "relevance".