This page explains how to test your account registration abuse integration.
On this page:To test your integration we allow you to send specific requests to force specific recommendations to be returned.
You should then ensure that you handle each of the possible recommended actions correctly.
These test recommendations are only supported in your sandbox account. See Authentication for how to use your sandbox account.
To force us to respond with specific recommendations send a request to the Registration endpoint, and set the customer.email or the supplier.email field to an email address with one of the email domains shown below.
| Email Domain | Recommendation Action |
|---|---|
| @qa-force-allow.com | ALLOW |
| @qa-force-prevent.com | PREVENT |
These values will only work in your sandbox account.
While it’s uncommon, even the most reliable networks can experience occasional delays. Your system should be resilient and maintain performance standards even during these rare instances of slow responses.
We recommend you test your system’s behaviour in response to abnormal increases in latency, whether it be from network problems or from Ravelin’s systems.
We provide a request header to help you test this.
To force requests to take at least a specified duration, add the Ravelin-Min-Latency header to the request,
with a specified delay in milliseconds.
This is only supported in your sandbox account.
For example, for a 1-second delay:
$ curl "https://api.ravelin.com/v2/registration" \
-H "Authorization: token sk_live_your_secret_key" \
-H "Ravelin-Min-Latency: 1000" \
-X POST
...
Was this page helpful?