Registered Users
Learn how to get registered users to your server via webhooks
This webhook service informs you about users who complete the registration step by visiting the purchase flows you offer on your sales site or product page on Zotlo Store.
When users complete the registration step on the sales site you created with the Zotlo Self Service service, this webhook is sent immediately. However, on Zotlo Store, this webhook will be sent only after the user's first purchase transaction. If a user makes multiple purchases, this webhook will be triggered only for the first transaction and will not be sent for subsequent transactions.
Setup the Endpoint URL
Webhook events are sent to your server via HTTP POST
. You configure the endpoint URL through Developer Tools / Webhooks menu under your project.
Webhook Events Sending Rules
The webhook notification for registered users will be sent within 5 minutes.Your server should return a 200 status code. Any other status code will be considered a failure by our backend, and the following retry process will apply:
If the first attempt fails, the next attempt will be made within 1 hour.
If the delivery fails again, it will be retried once per hour, up to a maximum of 10 attempts.
After 10 attempts, if the delivery is still unsuccessful, the process will be stopped.
The webhook for user registrations will be sent immediately if the user registers through Self Service, as mentioned above. In Zotlo Store, the webhook will be sent only after the user's first purchase. If the user makes multiple purchases, the webhook will be sent only for the first one and not for the others.
Events Format
Webhook events are serialized in JSON. The body of a POST
request to your server will contain the serialized event.
Fields
clientUuid
Unique ID of the registering user.
clientIp
IP address of the registering user.
language
Language used by the user.
storeRegister
It indicates the module: true
for Zotlo Store and false
for Zotlo Panel.
subscriberId
Subscriber ID associated with the transaction.It could be a phone number or an e-mail address.
subscriberName
Name and surname of the registered user.
appId
Project ID for the registration.
flowId
Flow ID for the registration.
siteId
Site ID for the registration.
registerDate
Date of registration, shown in UTC.
registerOtpStatus
It indicates whether there is an OTP step in the registration process. If true, there is an OTP step; if false, there is no OTP step.
Last updated