Use SMSVerifier API endpoints to list purchased virtual numbers, check their usage status, and retrieve SMS logs, enabling you to reconcile purchases with actual usage efficiently for billing audits.
Understanding Purchased vs Used Virtual Numbers
When working with SMSVerifier, it’s critical to distinguish between purchased and used virtual numbers to maintain accurate billing and audit trails.
Purchased virtual numbers are numbers you acquire through the API or dashboard, reserving them for receiving SMS OTPs or verification codes. However, not all purchased numbers receive an SMS immediately or at all.
Used virtual numbers refer to those that have successfully received at least one SMS message or OTP. Usage data includes details such as received SMS content, timestamps, and the service for which the code was sent.
Unused purchased numbers may still incur costs depending on your plan or provider. Tracking usage helps optimize spending and ensures you only pay for numbers that deliver value.
Key SMSVerifier API Endpoints for Tracking
SMSVerifier provides several API endpoints that enable you to track virtual numbers from purchase through usage.
- List active numbers: Use the
getNumbersaction to retrieve all numbers currently assigned to your account, along with their status. - Check number status and usage: The
getStatusendpoint provides information on whether the number has received SMS, is waiting, or expired. - Retrieve received SMS messages: The
getSmsaction returns the content and timestamps of SMS messages received on a specific number. - Balance and transaction logs: Use
getBalanceandgetOperationsto correlate your purchases and payments with number usage.
Combine getNumbers and getSms calls periodically to build a usage dataset that maps each purchased number to its actual OTP usage.
Best Practices for Reconciliation and Auditing
Reconciliation is fundamental for billing audits to ensure you are charged only for the numbers that were truly used.
- Maintain a usage database: Store API responses for purchased numbers and received SMS in your own system with timestamps.
- Regular reconciliation cadence: Perform daily or weekly audits to identify unused numbers and potential billing discrepancies early.
- Cross-reference services: Verify the service name or type linked to each number (e.g., WhatsApp, Telegram) to ensure the usage matches your expectations.
- Track expiry and refunds: Monitor numbers approaching expiry to claim automatic refunds for unused numbers.
Not reconciling frequently can lead to paying for numbers that were never used or expired without receiving SMS, increasing operational costs unnecessarily.
Automating Reconciliation with API and Webhooks
Automation is key to efficient reconciliation at scale. SMSVerifier supports API-driven automation and webhook notifications.
API polling
Schedule regular API calls to fetch number status and SMS logs for real-time usage tracking.
Webhooks support
Receive instant notifications when a new SMS arrives on a virtual number, reducing the need for constant polling.
Data integration
Integrate this data with your billing or ERP system for seamless audit reporting and chargeback management.
Use webhook callbacks to update your usage DB instantly, and fallback to periodic API calls for status checks on numbers without SMS to catch edge cases.
Handling Discrepancies and Refunds
Despite best efforts, discrepancies can occur between purchased and used virtual numbers. Here’s how to address them:
- Audit logs: Review your API transaction logs along with SMS receipt data before raising issues.
- Unused number refunds: SMSVerifier automatically refunds unused numbers if no SMS arrives within the standard expiry period (usually 20 minutes).
- Contact support: For unresolved mismatches or suspected billing errors, reach out to SMSVerifier’s support with detailed logs.
- Adjust your workflow: Refine your purchase and usage tracking scripts to avoid future mismatches.
Frequently asked questions
What API endpoints are essential for tracking purchased virtual numbers?
How can I differentiate between purchased and used virtual numbers?
Does SMSVerifier API provide detailed usage logs for reconciliation?
How often should I perform reconciliation to maintain accurate billing records?
Can I automate the reconciliation process using SMSVerifier API?
What should I do if I detect discrepancies between purchased and used numbers?
Are refund policies related to unused virtual numbers documented in the API?
Ready to track and reconcile your virtual numbers accurately?
Start integrating SMSVerifier API today to automate your billing audits and optimize your virtual number usage.
Read the API docs