Registration
Registration Blocks
Using this request you can get all registation forms configured in admin zone
/regform?all=true | GET |
Request params:
event_id | Event (Exhibition) ID |
Request example:
/regform?all=true&event_id=7 |
Response example:
{
"id": 1261
,
"name": "Contact Details"
},
{
"id": 1372
,
"name": "Other Info"
}
Registration Block Info
Using this request you can get a form in .xml format
/regform?section_id={{ id }} | GET |
Request params:
section_id | Block ID |
Request example:
/regform?section_id=1261 |
Registration Label Alias
Using this request you can get fields name (alias)
/api/registration/fields | GET |
Request params:
event_id | INT | Event (Exhibition) ID |
Response example:
{
"text-input-1494256475399": "First Name"
,
"select-1498236304134": "Please confirm the number of employees in your organisation"
}
Send Registration Request
Using this request you can send registration data to server
/registration | POST |
Request params:
event_id | Event (Exhibition) ID |
email* | User Email |
firstName* | User First Name |
lastName* | User Last Name |
gender | User Gender |
company | User Company Name |
position | User Job Title |
country | User Country |
city | User City |
nationality | User Nationality |
postcode | User Postcode |
tel | User Phone Number |
website | User Website |
address | User Address |
category_id | User Category ID |
external_code | User External Code |
organisationName | User Organisation Name |
organisationId | User Organisation Id |
exhibitor_id | Exhibitor ID (or external_id) to attach this account as team member to |
member_role | Team Member Role ('admin' or 'member') |
pass | User Password |
update | 1 | 0 (default). Set true to update account by email |
send_email | true | false (default). Set true to send registration email |
{{ Other custom fields from previous request }} |
Only the firstName lastName and email fields are required. The platform backend will respond with an HTTP/1.0 400 Bad Request if any of these three fields are left blank, are filled with incorrect data, or if the email is already in use. Otherwise the backend will respond with an HTTP/1.0 200 ОК. All other fields are optional. The password field is preferred, but not required. If left empty, a randomly generated password will be sent to the registered email address and the user will be prompted to change it upon first log in.