Short answer
The registration webhook automatically creates a buyer or supplier account in your system as soon as an external system sends the sign-up data via HTTP POST to your individual webhook URL. This lets you transfer registrations from your own form, a landing page or a third-party system directly into Leadnodes.
What does the webhook do?
The webhook is an interface to which an external system sends new user data. Leadnodes then automatically creates the appropriate account, assigns the default permissions (buyer or supplier) and asks the new user to confirm their email address before they can log in. The system administrator is informed about every new registration by email and notification.
How do I activate the webhook?
- Navigate to System settings > Branding settings.
- Open the SignUp Routes section.
- Activate the switch Allow buyer registration and/or Allow supplier registration.
- A webhook URL with a security token is displayed automatically. Copy it using the Copy button.
- Click Save settings and store the URL in the external system.
How is the webhook URL structured?
The URL always follows this pattern:
https://ihre-domain.de/api/webhooks/registration/{typ}/{token}
- {typ} – either
buyerorsupplier. The type determines the permissions assigned. - {token} – your secret webhook token. The buyer and supplier URLs share the same token.
Requests are sent via HTTP POST in JSON format.
How is the data structure (payload) built?
The user data is passed as JSON in the request body.
Mandatory fields
- company – company name (max. 255 characters)
- gender – salutation:
morf - first_name – first name
- last_name – last name
- phone – phone number
- email – valid email address
Optional address fields
- street – street
- house_number – house number
- zip_code – postcode (exactly 5 digits)
- city – city
- country – country
Optional login credentials
- username – username (letters, numbers, hyphens and underscores)
- password – password (min. 6 characters)
If the username or password is omitted, Leadnodes generates them automatically.
Example request
POST https://ihre-domain.de/api/webhooks/registration/buyer/{token}Content-Type: application/json{ "company": "Acme GmbH", "gender": "m", "first_name": "Max", "last_name": "Mustermann", "phone": "+49 30 1234567", "email": "max.mustermann@example.com", "street": "Hauptstrasse", "house_number": "12a", "zip_code": "10115", "city": "Berlin", "country": "Deutschland"}
Example response (success)
{
"message": "New user account successfully created.",
"user_id": 12345
}
Further frequently asked questions
What happens if the username is already taken?
The webhook does not reject the registration. Instead, a free variant is generated automatically by appending a number (e.g. mustermann becomes the username mustermann1). The account is therefore still created.
Does the new user have to confirm their email address?
Yes. After registration, the email address is initially unconfirmed. The user must confirm their address before they can log in.
Why do I receive the response “Registration disabled” (403)?
Registration for the requested type is deactivated. Activate the appropriate switch (buyer or supplier) under System settings > Branding settings > SignUp Routes.
Why do I receive the response “Invalid webhook token” (404)?
The token contained in the URL is invalid or has since been regenerated. Copy the current webhook URL from the settings again and update it in the external system.
What does error 422 mean?
The submitted data is incomplete or invalid (e.g. missing mandatory fields or an invalid email address). Check the payload against the mandatory fields listed above.
Can I change the webhook token?
Yes. Use Regenerate webhook token to create a new token. Warning: the previous webhook URLs become invalid immediately and must be updated everywhere they are used. Only do this if the token has been compromised.
Is there a request limit?
Yes. For security reasons, a maximum of 60 requests per minute per URL is allowed. If more requests are sent, they are temporarily rejected.