For a problem with an order, include
- The order ID. It is shown on the order page and in your order history. In the API it is the
idfield of the order. - The service and the country you ordered, for example WhatsApp in Indonesia.
- The time you placed the order, with your time zone.
- What happened. No number was issued, no code arrived, or the code or the number was rejected by the service.
With those four things we can find the order straight away. Do not send your password or a full API key. We never need either.
What does not need a ticket
- A refund for a code that never arrived. It is automatic. When an order closes without a code, the full price returns to your balance on its own. The rules are in the refund policy.
- Cancelling an order. You can cancel it yourself from two minutes after it starts, as long as no code has arrived. The price is refunded in full.
- A route that is suspended or not rated yet. The performance page shows the figure behind every route and explains the rule.
- General questions. How numbers work, how long they last and how pricing works are answered in the FAQ.
Do write to us if an order closed without a code and the refund is not in your balance. Send the order ID and we will look into it.
API and integration questions
Start with the quickstart. It takes you from an API key to a first verification code. Every error code is listed in the error reference, with what to do about it.
If you are still stuck, email us the request path, the error code you got back and the time of the request. Leave the API key out. The first characters of the key are enough to identify it.
Other reasons to write
- Your personal data. To see, correct or delete what we hold about you, write from the address on your account. The privacy policy lists what that is.
- Reporting misuse. If a FastOTP number was used against you or against your platform, send us the number and the date. Acceptable use is set out in the terms.
- Questions about the company. Who runs FastOTP, and the rule every route is held to, are described on the about page.