Last Update: 2024-03-21
<eventsubscribe id="" customerid="">
<address key="Email"></address>
<sendmail>1</sendmail>
<dates>
<date id="">
<escortcount></escortcount>
<escortname></escortname>
</date>
...
</dates>
</eventsubscribe>
| Element | Format | Description |
|---|---|---|
eventsubscribe["id"] |
varchar(30) | ID of event |
↳ address |
Add recipient from an existing address | |
↳ @key |
varchar | Key-field by which the address is specified |
↳ sendmail |
1|0 | Send confirmation mail(s) if definied |
↳ dates |
List of dates where the address should be subscribed | |
↳ @date |
Date | |
↳ @id |
ID of date | |
↳ @escortcount |
int | Number of escorts (if event configured to allow to enter a number of escorts) |
↳ @escortname |
varchar | Name of escort (if event configured to allow to enter a name of one escort).escortcount must be set to "1" in that case.For multiple escorts it is not possible to specify a name and this field will be ignored. |
<data>
<date id="1" code="7200">Ok</date>
...
</data>
| Code | Description |
|---|---|
| 2000 | Ok |
| 7204 | Error: subscription for event with payment not possible |
| 7205 | Error: subscription for ondemand events not possible |
| Element | Format | Description |
|---|---|---|
date |
Success or error message for a date | |
↳ @id |
ID of date | |
↳ @code |
Success or error code 7200 ... Ok 7201 ... Ok, but on waitinglist 7202 ... Error: outdated 7203 ... Error: booked up 7206 ... Error: already subscribed |