Influencer API · Endpoint Endpoint reference

Influencer Events API

Retrieve monitored creator events

Is there an API to retrieve monitored creator events?

Yes. The Influencers.club Events endpoint lists everything your subscriptions have caught — new posts, changes and milestones — as a queryable feed, so your systems can react to creator activity without polling profiles.

Verified against the live API in August 2026 Endpoint reference →

What this endpoint returns

Counted on the live search index, not modelled or rounded.

Measured August 2026

340M+

Searchable Influencer profiles

40+

Data points returned per creator

Platforms mapped in the social graph

Platforms with full discovery support

Request

Make the call

Both samples below are complete. Paste one in, swap the key, get a 200.

GET https://api-dashboard.influencers.club/public/v1/social/listening/events/

Auth Authorization: Bearer <API_KEY> Content type application/json Rate Included in monitoring (0.3 credits per creator per day) Full reference →

curl -X GET 'https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&event_type=new_post&page=1&page_size=10' \
  -H 'Authorization: Bearer YOUR_API_KEY'

import requests

res = requests.get(
    "https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&event_type=new_post&page=1&page_size=10",
    headers={"Authorization": "Bearer YOUR_API_KEY"}, ) print(res.json())

const res = await fetch("https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&event_type=new_post&page=1&page_size=10", {
  headers: { Authorization: "Bearer YOUR_API_KEY" }, }); const data = await res.json();

$ch = curl_init("https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&event_type=new_post&page=1&page_size=10");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["Authorization: Bearer YOUR_API_KEY"]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);

req, _ := http.NewRequest("GET", "https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&event_type=new_post&page=1&page_size=10", nil)
req.Header.Set("Authorization", "Bearer YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)

Response

What comes back

A 200 with the page of creators and your remaining credit balance. Creator values below are elided — field names and types are exactly as published in the API schema.

200 OKJSON

{
  "count": 42,
  "next": "https://api-dashboard.influencers.club/public/v1/social/listening/events/?page=2&subscription_id=1184",
  "previous": null,
  "results": [
    {
      "id": 90211,
      "event_type": "new_post",
      "event_value": {
        "post_id": "3982048237845084039",
        "post_url": "https://instagram.com/p/DdDE8ZHOfeH",
        "caption": "There’s never been a class that’s more excited about reading than this one",
        "likes": 193822,
        "comments": 30230,
        "views": 10580900
      },
      "creator": {
        "platform": "instagram",
        "platform_id": "2278169415"
      },
      "date_occurance": "2026-09-09T16:02:00Z",
      "created_at": "2026-09-09T16:04:09Z",
      "delivery_status": "sent",
      "latency_seconds": "129",
      "retries": "0"
    }
  ] }

Response fields JSON always returned · docs on request

Field	Type	Meaning
Envelope
count	integer	Total events matching the filter.
next · previous	string	Page URLs, null at the ends.
results[]	array	Events on this page.
Each event
id	integer	Event ID.
event_type	string	new_post · bio_change · follower_threshold · …
event_value	object	Type-specific payload — the post for new_post, old/new values for changes, the milestone for follower_threshold.
creator	object	platform and platform_id of the creator.
date_occurance	string	When the activity happened on the platform.
created_at	string	When Influencers.club recorded it.
delivery_status	string	pending · sending · sent · failed · retrying.
latency_seconds	string	Seconds from activity to detection.
retries	string	Webhook delivery attempts beyond the first.
Errors (400 / 403 / 429)
error_code	string	Machine-readable slug, e.g. insufficient_credits. Always present on errors — branch on this, not on error.
error	string	Human-readable description of what went wrong.
retry_after	integer	Seconds to wait before retrying a 429; mirrored in the Retry-After header.

event_value shape depends on event_type. GET /events/{id}/ adds the per-endpoint delivery history.

Parameters

The spec

Parameter	Type	Accepted values	Behaviour
GET /public/v1/social/listening/events/	endpoint	subscription_id, event_type, creator, page, page_size (query parameters)	Every activity your subscriptions have caught, with the event payload, which creator it concerns and the delivery status of the webhook. Fetch one event at …/events/{event_id}/ for its full delivery history. Reading events costs nothing beyond monitoring.
subscription_id	integer	Query parameter	Only events from one subscription.
event_type	string	new_post · bio_change · follower_threshold · …	Only one kind of activity.
creator	string	Query parameter	Only events for one creator.
page · page_size	integer	page_size defaults to 10	Pagination.

Billing. Reading events is free — it’s included in the 0.3 credits per creator, per day you already pay for monitoring. No credits are charged per call.

Recipes

How teams use this endpoint

Three ways this fits a creator-data workflow.

Pull the feed

Everything your subscriptions caught.

GET https://api-dashboard.influencers.club/public/v1/social/listening/events/?event_type=new_post

Check a delivery

One event with its full webhook history.

GET https://api-dashboard.influencers.club/public/v1/social/listening/events/90211/

Backfill after downtime

Re-read a subscription’s events instead of relying only on the webhook.

GET https://api-dashboard.influencers.club/public/v1/social/listening/events/?subscription_id=1184&page=1&page_size=50

Other creator data you can access

Influencer API endpoints

Tracking and Posts · 7

Campaigns Creator Posts Events Post Comments Post Details Post Transcripts Subscriptions

Platform coverage

Six platforms with full data, 40+ more in the social graph

Instagramdiscovery · full data

TikTokdiscovery · full data

YouTubediscovery · full data

X / Twitterdiscovery · full data

Twitchdiscovery · full data

OnlyFansdiscovery · full data

Plus Facebook, Pinterest, Reddit, LinkedIn, Discord, Snapchat,
Linktree and 40+ more via connected socials.

FAQ

Frequently asked questions

What does this endpoint cost?+

Nothing per call. Events are included in the 0.3 credits per creator, per day you pay for monitoring the creators that generated them.

Where can I find my API key?+

Create a free account. You will find your API key through the API side menu.

How do I retrieve monitored creator events using your API?+

Sign up for free and copy your API key from the dashboard. GET /public/v1/social/listening/events/ — filtered by subscription_id, event_type or creator if you like — to list everything your subscriptions have caught, each with its event_value payload, the creator’s platform and ID, when it happened, and the webhook delivery_status, latency and retries. GET /events/{id}/ returns one event. No per-call charge; it’s covered by the 0.3 credits per creator per day you pay for monitoring.

What are your pricing plans and what do they include?+

Paid plans start at $249/month and use a flexible credit-based model.

Each API call consumes a specific number of credits depending on the endpoint and data depth. You can compare all tiers, credit amounts, and per-endpoint costs in the Pricing section of our API docs.

How can I get in touch with your team?+

Book a time on our calendar to talk to someone from our team and learn about the full capabilities of our API.