January 2026 Update
18 days ago by Lorenzo Roveda
🔥 January Product Update: Auto Top Up keeps your API balance funded automaticallys, you can programmatically delete customer data via a new Delete Data API, and Phone to Name now returns enriched identity signals like Date of Birth and Addresses.
💳 Auto Top Up
Auto Top Up helps keep your API key balance funded automatically, so you can avoid failed requests caused by low credit.
🔍 Key Features
- 💳 Payment methods management: Add and manage cards directly from the Payment Methods section.
- ⚙️ Configurable rules: Set a low-balance threshold and top up amount.
- 💰 Monthly maximum limit: Control spending with a configurable monthly cap.
🗑️ Delete Data API (New endpoint)
You can now request deletion of previously enriched data referring to a specific claim and customer_id.
🔍 Key Features
- 🧩 Claim-specific deletion: Request deletion for a single product/claim (for example
score,email,phone,domain,bot_detection,login). - 🧾 Simple inputs: Provide the
claimandcustomerIdof the previous call you wanted to delete. - ⏳ Asynchronous processing: A successful response confirms the request was accepted, and deletion is processed in the background.
📊 Example Output
{
"status": "ok",
"message": "deletion request accepted - the deletion will be processed shortly"
}📱 Phone to Name: New signals
The Phone to Name endpoint now returns enriched identity information, including Date of Birth and Addresses linked to a phone number.
🔍 Key Features
- 🧾 New signals:
names_dobsandnames_addressesare now included when found. - 🔎 Multi-source enrichment: Each value is returned with an occurrence
countacross sources. - 🧩 Same inputs: Continue using
transaction_idandphoneas input.
📊 Example Output
{
"names_dobs": [
{
"value": "1985-05-15",
"count": 1
}
],
"names_addresses": [
{
"value": "Via Gustavo Fara, 9",
"count": 2
}
]
}📚 Resources
- Phone to Name API Reference - Learn more on Phone to Name endpoint
- Delete Data API Reference - Detailed guidance to use Delete Data API