​

RND Safe-Harbor Pre-Contact Number Scrubbing

• GET /compliance/rnd/check — one E.164 number plus the date you obtained (or last verified) prior-express consent, returning an FCC RND verdict and whether the safe harbor applies.

​

How RND differs from the other scrubs

​

Enable the per-org toggle

{
  "error": {
    "code": "RND_SCRUB_NOT_ENABLED",
    "status": 403,
    "details": { "flag": "organizations.settings.rnd_scrub_enabled", "feed_synced": false }
  }
}

curl "https://api.orbit.devotel.io/api/v1/compliance/rnd/settings" \
  -H "Authorization: Bearer $ORBIT_API_KEY"

{
  "enabled": true,
  "feed_synced": true
}

​

Feed status — feed_synced on every verdict

• true — the ingested RND snapshot backed this verdict (real data).
• false — no feed is loaded, or the feed lookup itself failed. Verdict degrades to no_data on every number, and safe_harbor is false — we cannot claim a sync we did not complete. Never treat a false response as a real “not reassigned” answer; treat it as UNKNOWN and gate the send.

​

Single-number check

curl "https://api.orbit.devotel.io/api/v1/compliance/rnd/check?phone=%2B14155550101&consent_date=2026-08-15" \
  -H "Authorization: Bearer $ORBIT_API_KEY"

• phone — E.164 destination (leading +, 7-15 digits).
• consent_date — ISO calendar date (YYYY-MM-DD) you obtained or last verified prior-express consent.

{
  "data": {
    "status": "no",
    "safe_harbor": true,
    "last_disconnect_date": "2025-11-02",
    "consent_date": "2026-08-15",
    "feed_synced": true,
    "reason": "No permanent disconnect after the consent date; the FCC reassigned-number safe harbor applies — safe to contact."
  }
}

​

Pre-campaign batch pattern

1. Build your segment with the audiences/CDP tools as usual.
2. Resolve a consent date per recipient — the date you obtained (or last verified) prior-express consent. One date per segment, or per contact if consent ages diverge.
3. Check the gate — GET /compliance/rnd/settings. If enabled or feed_synced is false, fix that first (above).
4. Loop the segment and call /rnd/check per number. The endpoint shares the standard authenticated-read budget (120 requests/minute per organization). Chunk the audience and call sequentially with a small pause (~500 ms) per request; a loop that fires in a tight burst hits HTTP 429 and pauses.
5. Route the verdicts out of the send audience:
   • yes → suppress the destination (and log it under your suppression layer so future segments exclude it up front). Do not attempt to send.
   • no_data → treat as UNKNOWN: either hold until the feed is synced or send under your own risk policy — it is not a safe-harbor pass.
   • no → eligible for the campaign (safe harbor covers it).
6. Launch against the scrubbed audience — see Outbound dialer campaigns and Campaign end-to-end.
7. Re-scrub stale audiences. The RND is updated by carriers continuously, so re-run before each send for an audience held more than a couple of days. The verdict you ran at audience-build time ages out as disconnect records move.

​

Failure modes and per-number handling

• Bad phone / bad consent_date → HTTP 422 with the failing field(s) in details. Fix the shape and retry; the verdict layer never sees it.
• Feed lookup fails or no feed is loaded → status: "no_data", safe_harbor: false, feed_synced: false, and last_disconnect_date: null. Route no_data per your own risk policy — it is never a safe-harbor pass.
• Unparseable consent date at the verdict layer → no_data with a specific reason; the controller’s YYYY-MM-DD regex keeps this from reaching the verdict in normal use, but an old SDK that skips validation gets the same safe degradation.
• HTTP 403 RND_SCRUB_NOT_ENABLED on every call → the per-org opt-in is off; the dashboard’s scrub card greys or enables the action up front via GET /compliance/rnd/settings.
• HTTP 409 RND_FEED_NOT_CONFIGURED on enable → the FCC feed is not ingested; the toggle cannot turn on yet. This is the gate at work, not a failed call.

​

Audit and logging caution

• DNC Scrubbing — the opt-out registry layer.
• Phone Deactivation Scrubbing — the carrier disconnect/churn layer, including the scrub-vs-send-gate comparison table above.
• Send Gates — the quiet-hours / DNC / RND / RMD gates that run at send time.
• Opt-Out & Suppression Lists — the layer a yes verdict routes onto.
• Your Tenant Compliance Posture — the toggle map, including the RND-scrub row.
• API Reference → Compliance — full request/response schemas.