POST /verifications
Creates a challenge that will be presented to a user. The challenge could be presented in a synch way, that is redirecting the user to the challenge being created, or in an asynch way, that is sending him a mail with the invitation to the challenge process. Swithching between those two cases is done providing (or not) the email parameter described later.
Parameters (bold ones are mandatory)
- api_key: API-Key to create the verification
- transaction_id: Your arbitrary ID for identifying the verification. It's useful for pairing verifications in you app
- notification_callback: Email or URL which will receive verification details. By default it's sert to API-Key's notification_callback
- email: If you want the user to access the verification challenge URL by his email define here his address
- return_url: when using an email as notification_callback you can specify this URL to get a "Continue to Your Company" link at the end of the
Results
Results when asking for HTML Page showing "we have sent you an email to client@example.com" when notification_callback is an email Redirect to verification's URL when notification_callback is an URL. Return codes for XML
- 201 Created: Verification successfully created. HTTP header Location contains verification's URL
- 400: Errors