A practical starting point for the ThickVerify API
The customer API supports ThickVerify’s virtual number workflow. Your application can retrieve catalogue information, check prices, purchase a number and follow the resulting activation.
Start with documentation and a customer key
Sign in and open API Docs. Read the authentication instructions and generate your customer API key in Settings when you are ready to integrate.
Keep the key on your server. Do not put it in public browser JavaScript, share it in screenshots or include it in a URL.
Begin with read-only requests
Start by checking your balance and retrieving the service and country catalogues. Use the returned identifiers when requesting a price.
Treat availability as a snapshot. Your application should display the selected service, country and total clearly before a user proceeds to a purchase.
Handle purchases deliberately
Follow the purchase endpoint’s documented requirements, including its maximum-price limit and idempotency key. Use a unique key for a new intended purchase and follow the documentation when retrying the same request.
If a response is interrupted, check order history rather than assuming the purchase failed. A browser or network timeout does not by itself confirm that no order was created.
Track the order, not just the request
Use the local order ID returned by ThickVerify to request status and SMS updates. Respect the polling interval and account rate limits listed in API Docs.
The API documentation describes eligible cancellation and history requests as well. This API guide covers virtual numbers; it does not imply that email activations, account listings or subscriptions have the same API support.