Provides the times in UTC that a telephone call can be placed
for a given phone and date
GeoScrub
Legal Call Times for Date
Get the legal calling windows for a phone number on a specific date
POST
Provides the times in UTC that a telephone call can be placed
for a given phone and date
How calling windows are determined
The endpoint returns the legal calling windows for the called party’s local time, applying these rules in priority order:- Project-level override — calling-hour rules you’ve configured against your
DNCProjIdfor a given state in the DNCScrub Portal. Use this when your brand wants stricter rules than law requires. - State law overlay — state-specific telephone solicitation curfews tracked by Contact Center Compliance. For example, Alabama is 8 AM – 8 PM with no Sunday calls; California is 9 AM – 9 PM all 7 days; Florida is 8 AM – 8 PM. State laws are maintained by our in-house compliance counsel and updated as legislation changes — no client-side change is required.
- Federal baseline — applied when no state overlay exists. US numbers default to FCC TCPA: 8 AM – 9 PM, all 7 days, called-party local time. Canadian numbers default to CRTC: 9 AM – 9:30 PM weekdays, 10 AM – 6 PM weekends.
00:00–00:00 for a given day means no calling allowed that day (e.g. Alabama, Louisiana, Mississippi forbid Sunday telephone solicitations). The response will include zero windows for that day.
The response reflects residential telephone solicitation curfews. B2B calls have different rules in some states (full exemptions, narrower windows, etc.) — this API does not apply B2B exemptions. If your call list is exclusively to businesses, apply that logic on your side.
Response Fields
Every input phone produces exactly one entry inLegalCallTimes. Inspect Status to decide how to handle each row.
Status Values
We deliberately do not guess a timezone for
UNKNOWN_NXX numbers: a wrong “legal to call” answer driven by a guessed timezone is TCPA exposure, and silently approving calls to nonworking numbers would hide data quality problems on your side.
Per-row
Status replaces the older behavior where a single bad phone caused the entire batch to return HTTP 400. The endpoint now returns 200 with one row per input phone; inspect Status to decide which rows are usable. HTTP 400 is still returned for batch-level errors (missing body, empty list, more than 1000 phones).