broadcastifyassist: the interface scannerassist expects ======================================================== broadcastifyassist wraps the Broadcastify Calls API (https://bcfy.io/dev/). Broadcastify's developer terms restrict sharing tools built on the API, so its source isn't published. This file describes what it does, so you can write your own. scannerassist makes exactly one call: broadcastifyassist -a group-archives -g GROUP [-g GROUP ...] -s START -e END [-F] -v and expects a JSON array of calls on stdout, oldest first, one object per radio transmission: [ { "groupId": "5000-1", "ts": 1794030377, "start_ts": 1794030373, "end_ts": 1794030376, "duration": 3, "skew": 0.755, "freq": 856.9375, "src": 3135118, "nodeId": 6644, "url": "https://calls.broadcastify.com/5g2esqtq/6644/1794030373-1.mp3", "label": "arl-police-dispatch", "start": "2026-11-07 00:46:13" } ] The fields scannerassist uses: groupId talkgroup, as - ts when Broadcastify logged the call (Unix seconds); with groupId, it identifies the call start_ts when the transmission started (Unix seconds) start start_ts as local wall-clock time; scannerassist prints it duration seconds src radio ID of whoever was talking (may be missing) url the audio file; a plain download, no auth needed label the group's alias, or its groupId if it has none Everything except label and start comes straight from the API's /calls/v1/group_archives/{groupId}/{start}/{end} endpoint. The wrapper adds those two, and: - accepts several -g values and merges the results into one timeline, sorted by start_ts - takes -g as a group ID or an alias (see below) - takes -s/-e as local wall-clock time ('2026-11-09 21:30') or Unix seconds; one TIMEZONE setting in its config file decides the zone for both reading -s/-e and writing start (mine is America/New_York) - splits windows longer than 8 hours (the API's limit) into several requests - refuses windows over 2 hours without -F, since the API bills per call returned (about $0.60 per 1,000) - pads each window by 30 seconds and keeps calls whose start_ts falls inside it (the API filters on ts, which lags the start) - caches results for windows that ended more than 15 minutes ago Aliases live in a plain text file, one per line. A target is a group ID or another alias, so an alias can name a set of groups: arl-police-dispatch|5000-1 arl-police-motors|5000-11 arl-police-events|5000-20 arl-police|arl-police-dispatch,arl-police-motors,arl-police-events The full usage, for reference: broadcastifyassist -a group-archives -g group [-g group ...] -s start -e end [-F] [-v] # group|start|duration|src|url broadcastifyassist -a group-get -g group [-g group ...] [-v] # group|display|description|category|tag|first_seen|last_seen broadcastifyassist -a call-get -g group -t ts [-v] # group|start|duration|src|url broadcastifyassist -a src-get -i sid-radio [-v] # src|description|group|last_seen|calls broadcastifyassist -a node-get -i node [-v] # node|type|system|site|county|state|calls_per_min|calls broadcastifyassist -a sids [-R] [-v] # sid|name broadcastifyassist -a system-groups -i sid [-m max] [-R] [-v] # same as group-get broadcastifyassist -a aliases # alias|group,group,... broadcastifyassist -a token -g group ID (5000-1) or an alias; repeatable -s/-e local time ('2026-11-09 21:30', zone from config) or Unix seconds -F allow group-archives windows over 2 hours -m highest talkgroup number to scan (default 160) -R refresh the cached sids or system-groups list -v raw JSON instead of |-delimited output