Viber Activity Checker API Workflow for Automated Checks
Of all the checks in this stack, activity is the one whose data expires fastest. A format from March can still be trusted in July. An activity tier...
Julian works on verification API integrations, batch jobs, CSV workflows, task polling, retry handling, result exports, and developer documentation. His guides explain how teams can integrate verification APIs safely and connect results with internal data systems.
View full author profile →Of all the checks in this stack, activity is the one whose data expires fastest. A format from March can still be trusted in July. An activity tier from March is a guess, because accounts go quiet on their own schedule. That is why the API route for Viber Activity is not a convenience. It is the core of the workflow. Viber Activity Checker is the ZelNum page that supports this job: Viber Activity Checker.
Quick answer
Submit the list through the API, receive the activity tier per record, and store it with a checked timestamp. Re-run on a schedule and compare tiers between runs. The output is not a single snapshot. It is a drift line: how many active rows went quiet, how many inactive came back.
The API workflow
- Submit the job. One request per batch, carrying the record set and a stable record ID per row.
- Poll or receive callbacks. Polling is fine at low volume; webhooks pay off when you act on results immediately.
- Store per record. Keep the activity tier, the country if relevant, and the checked timestamp together with the record ID.
- Compare runs. The movement between runs is the real output of the pipeline.
Keep the first call small. Submit a handful of records, confirm the response shape, then scale.
The drift line
Here is what a quarterly run looks like over three checks:
| Run | Active | Inactive | Not on Viber |
|---|---|---|---|
| January | 58% | 27% | 15% |
| April | 54% | 31% | 15% |
| July | 51% | 34% | 15% |
(These figures are illustrative, not a product performance claim.)
The active share is sliding and the inactive tier is growing. That is not three snapshots. It is a warning that the list is cooling, and the campaign should be sized accordingly. A single registration check would never show this.
Webhooks or polling?
Polling on a short interval is simpler for most teams. If you use webhooks, make the callback idempotent: processing the same event twice must not double-charge or double-write. One missed callback should never create a second paid job or overwrite a clean result with a blank one.
Export fields that matter
| Field | Why it matters |
|---|---|
record_id |
Joins the result back to the source. |
activity_tier |
Active / inactive / not on Viber. |
checked_at |
The timestamp that makes the drift line possible. |
status / reason |
The routing decision and why. |
Drop checked_at and the pipeline stops being a time series. Keep it and every future run adds to the trend.
Mistakes to avoid
- Automating the check but not the response. A chart nobody reads is decoration. Route the tiers into the campaign workflow, or the schedule is just a report generator.
- Treating the last run as the current truth. An active tier from March is a guess by July.
- Comparing runs without timestamps. Two snapshots without checked timestamps are just two numbers; the trend needs the time axis.
FAQ
Why is the schedule the core of an activity check?
Because activity decays on its own. The value of the API is that it re-checks on a schedule and shows the drift, and drift is what the campaign decision runs on.
How often should the API run?
Monthly is a good baseline for a list you send to regularly; quarterly for a deep re-check. The interval matters less than the fact that there is one.
Webhooks or polling?
Polling for most teams. It is simpler, has fewer failure modes, and latency is irrelevant at low volume.
What does the drift line tell me?
It tells you whether the list is cooling or warming, and at what rate. That is the input for sizing the campaign and timing re-engagement.
What happens to unknown rows?
They wait for a retry. Unknown is not dead, and a later run often resolves it.
Related ZelNum pages
- Bulk Viber Activity Checker: CSV Upload and Result Export Guide for the file format details.
- Viber Activity Checker Use Cases for how different teams read the same export.