Ansible Gateway is an interface for delivering verification codes through the messenger. Public pricing and open onboarding have not been published. For website sign-in, use Ansible authorization.
Check the sending result against its request ID rather than treating an HTTP response as proof of delivery.
Before integrating, verify the required methods and access permissions in the agreed environment.
The recipient needs access to their Ansible account and an internet connection. Open Gateway sending has not been announced.
External Gateway top-ups are not enabled. Internal Ansible transactions use Diamonds.
Public code delivery prices and balance conditions have not been announced.
Refund rules will be published with onboarding terms; refunds are not guaranteed in advance.
The reference describes request IDs and delivery statuses. Their availability must be checked in the specific integration.
Keep tokens, codes and personal data out of public source code and logs. Follow the privacy rules.
The user should understand which service requested the code and which action is being confirmed.
Use the Bot API for bot interactions. Gateway is not permission to send advertising.
Internal Ansible transactions use Diamonds; no code delivery price has been published.
The user voluntarily provides a number to your service for the selected action.
Yes. Do not send unwanted codes or messages.
The reference uses international E.164 format.
Open Gateway testing has not been announced. For website sign-in, see the OAuth documentation.
Public Gateway top-ups are not currently available.
The reference describes checkSendAbility; access is provided separately.
Do not share the code. If you did not initiate the action, do not confirm it.