The segment a save answered with, by its id, run again: the
same answer as POST /v1/{country_code}/segments — filters as interpreted, count,
exportable_count, facets, sample, prospecting, sources — with the stored segment
under segment. The count is today's, and its windows count from today, so
head_office_moved_within_days: 182 covers the 182 days before sources.relative_to, not
before the day it was saved.
A segment saved with sole traders lists them under its stored acknowledgement, repeated as
prospecting.acknowledgement; you do not send it again. facet_limit goes in the query string,
?facet_limit=20, 1 to 100 and 10 by default; any other value is 400 invalid_request,
and nothing is counted.
read -rs FIRMUS_KEY && export FIRMUS_KEY
curl -s -H "Authorization: Bearer $FIRMUS_KEY" \
"https://api.firmus.sh/v1/fr/segments/1?facet_limit=20"One call — on Free, one of the month's 1 000 lookups. A segment of another organization and
an id that never existed are both 404 not_found, and cannot be told apart. A server that
cannot count segments yet answers 503 segment_index_unavailable, and counts nothing.