Number Recycling

Check whether a phone number has been deactivated and reassigned to a new subscriber since a date you specify.

Benefits

Phone numbers churn constantly — when a subscriber leaves, their number is quarantined and later handed to someone new. The problem: old accounts often still trust that number for login, OTP, or recovery. Number Recycling flags when a number has changed hands since a reference date, so you can catch the stale-number risk before a recycled number becomes a silent account-takeover path.

How it works

You supply a number and the date you last trusted it; the operator tells you whether it has been reassigned since.

Your backend sends the phone number and a reference date.
The operator checks whether the number was deactivated and reassigned after that date.
You receive a clear signal — recycled or not — to feed into your trust logic.

Use cases

Account-takeover prevention — re-validate numbers on dormant or high-value accounts before allowing login, reset, or OTP delivery to a number that may no longer belong to the original user.
Recovery-flow hardening — block SMS-based recovery to numbers that have changed hands, closing a common fraud entry point.
KYC re-verification — periodically confirm a customer's number on file still maps to the same subscriber, keeping identity records trustworthy over time.
Database hygiene — identify recycled numbers across your user base to prune or re-confirm stale contact records.

Quick start

With an access token (see OAuth2 with Konera), check a sandbox number against a reference date:

curl -X POST https://api.pxg.konera.com/camara/number-recycling/v1/check \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"phoneNumber": "+14155550123",
"specifiedDate": "2024-01-01"
}'

Successful response:

{ "recycled": false }