SocialCrawl

Which call tells me when something is new?

The ways to know what changed, and which one fits a topic, an account, a page or a post.

This page is the choice. Webhooks and events is how the result reaches you.

Which call tells me when something new appears?

To be told when something new appears, match the ask to its job: for a recurring digest of what is new about a topic, keyword or brand, every 1h or slower, call POST /v1/search/everywhere with schedule (every 1h or slower, dry_run first), at 20 credits a search per fire and only rows that watch has not delivered, read through GET /v1/events, a webhook endpoint or the watch's own last_fire; for the new posts or comments of an account or post you already know, call POST /v1/monitors with webhook_rows: "new"; for a one-off check of what is new since your last check, on an endpoint that takes since or since_id, call the endpoint's own since or since_id (for example GET /v1/twitter/tweet/replies with since_id, which returns an empty list and costs nothing when nothing is new); for metric snapshots of accounts you name (followers, views, likes), taken on a schedule, call POST /v1/monitors with a track metric; for reading what your watches produced, from a feed you poll or an endpoint that receives a signed push, call GET /v1/events with a named consumer for reading, and /v1/webhook-endpoints for push; for what a keyword or boolean topic listener would cost each month and how it reads the rule, before it is created, call POST /v1/listening/streams?dry_run=1 with the listener body, which costs 0 credits and creates nothing; for each new mention of keywords or a boolean topic delivered one by one, every 30 minutes or slower, with boolean groups, a monthly cap and usage per client, and with comments: "new_posts" the comments under the Reddit posts it keeps, call POST /v1/listening/streams?dry_run=1 to price it, then POST /v1/listening/streams to create the listener; for the new posts of up to 300 named business, brand, creator or organisation accounts that match a topic, every 30 minutes or slower, call POST /v1/listening/streams?dry_run=1 with accounts (each a platform:handle such as reddit:nasa or youtube:@Google, or a profile URL), schedule.purpose (business, brand, creator or organisation) and keywords, then POST /v1/listening/streams to create the listener; for what is new on your listeners since the last read, in a later session or on a schedule you run yourself, call GET /v1/events with a named consumer and types=mention.*, then acknowledge each page with its pagination.next_cursor. A watch checks on a schedule and reports what that check found. Read what a watch produced with the event feed or receive it at a signed webhook endpoint; the schedule is explained in discover schedules and the account watch in Monitor webhooks.

Which one fits?

You want to know aboutCallRead it from
A digest of what is new about a topic, keyword or brandPOST /v1/search/everywhere with scheduleEvent feed or a webhook endpoint
Each new mention of a keyword or boolean topicPOST /v1/listening/streams (price it first with dry_run=1)GET /v1/events with types=mention.*
New posts from named accounts that match a topicPOST /v1/listening/streams with accountsGET /v1/events with types=mention.*
New posts or comments of an account or post you knowPOST /v1/monitors with webhook_rows: "new"Monitor webhooks
Metric snapshots of accounts you name, on a schedulePOST /v1/monitors with a track metricEvent feed
What is new since your own last check, on one endpointThe endpoint's since or since_idThe response itself

A page emptied by since or until is still billed. To pay only when something is new, use Listening or Monitors.

One more way: ask the endpoint for what is new

On an endpoint that takes since or since_id, send the value from your last read. GET /v1/twitter/tweet/replies with since_id returns an empty list and costs nothing when nothing is new. On a search or discover answer, send since_watermark with the data.next.watermark of your last answer.

On this page