API review

Jungler API review

LinkedIn engagement and social-intent signals: tracks profiles, company pages, posts and keywords every 24 hours, enriches each engager with profile, company and work-email data, and pushes ICP-filtered lists to Clay, HeyReach, Slack, Sheets or webhooks; REST API on every plan, priced by credits. Best for capturing the people who react to or comment on your own, competitors' or influencers' LinkedIn posts, enriched with work emails at no extra cost.

Verified 25 Oct 2026 · 25 endpoints listed

What a call costs

The actions you pay for, as Jungler prices them in credits.

ActionCostPer
New post found by a signal1 creditper post
New reaction or comment collected1 creditper engagement
Enrichment, work emails, exports, integrationsfree

Pricing, plan by plan

US dollars, as Jungler's pricing page shows them on 25 Oct 2026. Monthly and annual billing are shown apart.

Free tier 7-day free trial with 2,000 credits and a preview of Discovery, no credit card; nothing charged at the end (pricing FAQ).

Starter

$99/mo

billed monthly

$79/mo

billed annually

8,000 credits a month ($99 monthly / $79 yearly) or 16,000 ($159 / $127); 5 signals; work emails; unlimited team seats; integrations, webhooks, API

API included
Plan details

none: signals pause when credits run out

Discovery

$199/mo

billed monthly

$159/mo

billed annually

20,000 credits ($199 / $159), 30,000 ($299 / $239), 40,000 ($399 / $319); 15 signals; B2B creator discovery; 100 profile opens a month

API included

Growth

$299/mo

billed monthly

$239/mo

billed annually

20,000 credits ($299 / $239), 30,000 ($399 / $319), 40,000 ($449 / $359), 50,000 ($499 / $399), 60,000 ($549 / $439); 40 signals; 300 profile opens a month

API included

Enterprise

Custom quote

custom credits, signals and profile opens; dedicated support; book a demo

API included

Yearly is 20% cheaper, paid in one payment with the year's credits up front. 30-day money-back on the first payment if under two thirds of a month's credits are used.

Rate limits

Per endpoint per minute: workspaces and signal list 30; signal get/run, posts, engagers, run status, schedule reads 60; signal create/activate/deactivate/delete 6; workbook create, schedule create/cancel 30; tools 500.

More on limitsLess

429 on excess; exponential backoff advised.

How to get an API key

Jungler uses API key. The steps below follow Jungler's own docs.

  1. Create a Jungler account. API access starts on the Starter plan.
  2. app.jungler.ai/settings/integrations > Create API Key (shown once). Every request needs a workspace_id from GET /api/workspaces.
  3. Send it with every request: header X-API-Key.
  4. Make a first call: List workspaces. Keep the key in an environment variable, never in the command.
    curl -X GET "https://production.viacurrent.com/api/workspaces"

Where the docs live

WhatWhere
Documentationdocs.jungler.ai
API referencedocs.jungler.ai/api
llms.txtjungler.ai/llms.txt
Base URLhttps://production.viacurrent.com

Strengths and limits

Where it fits

  • Capturing the people who react to or comment on your own, competitors' or influencers' LinkedIn posts, enriched with work emails at no extra cost
  • Feeding engagers to Clay, HeyReach, Expandi, Slack or Google Sheets on a daily schedule
  • Finding B2B creators your buyers engage with (Discovery plan)
  • Teams that cannot connect a LinkedIn account: it works from public data via third-party providers, no cookies or extension

Where it falls short

  • Real-time alerts: signals refresh every 24 hours and webhooks deliver once a day
  • Sending outreach itself: it hands contacts to sequencers
  • Agent use through MCP: no MCP server is documented (source: docs.jungler.ai sitemap, 2026-10-25)
  • Engagement older than 180 days: engagers are archived after 180 days

Worth knowing

  • The API base URL is production.viacurrent.com, not a jungler.ai host.
  • Signal creation is limited to 6 a minute; the first run starts automatically and is polled via /signals/{id}/run.
  • Engagements are only for profile and company signals, not keyword signals.
  • Webhooks cap at 10,000 records per daily sync; too many high-volume signals in one config can lose data (same source).
  • Running out of credits pauses signals; you are never charged extra (pricing FAQ).
1 moreShow fewer
  • Not to be confused with jungler.io, an unrelated Italian influencer-marketing agency.

Who should use it

Use Jungler for
Capturing the people who react to or comment on your own, competitors' or influencers' LinkedIn posts, enriched with work emails at no extra cost
Look elsewhere for
Real-time alerts: signals refresh every 24 hours and webhooks deliver once a day

If Jungler is not the answer

Other Signals tools in this directory, each with its own review.

Before you build

Four things to settle first, each read off Jungler's own pages.

  • Confirm the API is on your planAPI access starts on the Starter plan. Free tier: 7-day free trial with 2,000 credits and a preview of Discovery, no credit card.
  • Keep the key out of your codeAPI key. It is sent as: header X-API-Key.
  • Design around the rate limitPer endpoint per minute: workspaces and signal list 30; signal get/run, posts, engagers, run status, schedule reads 60; signal create/activate/deactivate/delete 6; workbook create, schedule create/cancel 30; tools 500.
  • Know the catch before you scaleThe API base URL is production.viacurrent.com, not a jungler.ai host.

Want us to build it for you?

Tell us what you want Jungler to do in your stack. We will show you how we would wire it into your data, outbound or CRM, and what we would check first.

Read from jungler.ai/pricing, docs.jungler.ai/api and docs.jungler.ai/api/quick-start. Verified 25 Oct 2026.

All 25 endpointsFor developers: method, path, what it does and what it costs.

Base URL: production.viacurrent.com

Bulk and async: Workbooks extract engagement for specific posts as async runs (poll run status or receive a callback); schedules repeat them.

Webhooks: Daily delivery (first about 24 hours after creation), batches of up to 500 records every 2 seconds, max 10,000 records per sync (data beyond can be lost on high-volume configs); up to 3 custom headers; historic sync none/1/7/31 days once; a 4xx response stops the webhook until you edit it. Events: Posts, Engagements (reactions and comments; profile and company signals only), Workbook run callbacks

25 endpoints
MethodPathWhat it doesCost
GET/api/workspacesList workspacesNot stated
GET/api/workspaces/{workspace_id}/subscriptionGet workspace subscriptionNot stated
GET/api/signalsList signals (filter by query_type, is_activated)Not stated
GET/api/signals/{signal_id}Get a signalNot stated
POSTasync/api/signalsCreate a keyword, profile or company signal; first run starts automaticallycollecting data uses credits: 1 per new post and 1 per new reaction or comment
GET/api/signals/{signal_id}/runRun status of a signalNot stated
PUT/api/signals/{signal_id}/activateActivate a signalNot stated
PUT/api/signals/{signal_id}/deactivateDeactivate a signalNot stated
DELETE/api/signals/{signal_id}Delete a signalNot stated
GET/api/postsList and filter posts (sentiment, author function, role level, company size, industry, dates); snapshot_time pagination; has_engagement_since for incremental syncNot stated
GET/api/posts/{post_id}Get a postNot stated
GET/api/engagers/signal/{signal_id}Engagers (comments and reactions) for a signalNot stated
GET/api/engagers/post/{post_id}Engagers for a post; captured_after cursor for incremental syncNot stated
GET/api/engagers/signal/{signal_id}/contactsDeduplicated, enriched contacts for a signalNot stated
GET/api/engagers/workbook/{workbook_id}Engagers for a workbookNot stated
GET/api/engagers/workbook/{workbook_id}/contactsDeduplicated contacts for a workbookNot stated
POSTasync/api/workbooksCreate an immediate extraction run for specific posts (optional webhook callback)1 credit per post added plus 1 per engagement fetched
GET/api/workbooks/runs/{run_id}Get run statusNot stated
GET/api/workbooks/{workbook_id}/runRun status by workbook id (compatibility)Not stated
POST/api/workbooks/schedulesSchedule a workbook runNot stated
GET/api/workbooks/schedulesList schedulesNot stated
GET/api/workbooks/schedules/{schedule_id}Get a scheduleNot stated
DELETE/api/workbooks/schedules/{schedule_id}Cancel a scheduleNot stated
GET/api/tools/social-url-timestampRead the timestamp encoded in a social URLNot stated
GET/api/tools/parse-nameParse a person nameNot stated