View source for Pre-fill data in ticket shop

If you already know some information about your attendee, you might want to spare him the work of entering everything himself in the ticket buying process.
Typical use-cases are:
* - You have a logged-in area for your customers
* - You send out an email campaign to invite known customers
* - You want to invite a customer who just bought a ticket to buy another ticket or product in a different ticket shop

We currently offer two solutions to pre-fill the forms of the ticket shop:
# 1. via API
# 2. via URL parameter

==Pre-fill data via REST API==
'''Solution 1''' involves creating a new purchase with our REST API, set all the data in the appropriate fields and display the ticketshop as IFrame to the customer to finish his purchase (or even do the full purchase for him via API if it is a free ticket).
If you are interested in this solution, please have a look at our How-To: [[How-Tos#Pre-fill_the_ticketshop_with_buyer_data_via_REST_API|Pre-fill the ticketshop with buyer data via REST API]]

==Pre-fill data via URL parameter==
For '''solution 2''', you append the data you know to the URL of the event page (or IFrame). The customer will see the normal ticket selection screen and as he progresses in the purchase, the forms will be pre-filled (e.g. with his personal billing address).

'''Sample:'''
https://www.xing-events.com/YourEventIdentifier.html?field_paymentFirstname=Jon&field_paymentLastname=Doe<br/>
If a user opens this link (replace "YourEventIdentifier" with the identifier of your event), the Name "Jon Doe" will be pre-filled in the billing address form.

'''This is the list of supported parameters:'''
{| cellspacing="0" cellpadding="2" border="0" style="width: 933px;" class="properties"
|-
! bgcolor="#cccccc" align="left" scope="col" | Parameter<br> 
! bgcolor="#cccccc" align="left" scope="col" | Description<br>
|-
| colspan="2" | '''Standard fields at billing address step:''' 
|-valign="top"
| field_paymentSalutation
| Salutation of attendee at billing address step (0=Mr, 1=Ms., 2=Mrs.)
|-valign="top"
| field_paymentTitle
| Title of attendee at billing address step (Dr., Prof., ...)
|-valign="top"
| field_paymentFirstname
| First name at billing address step
|-valign="top"
| field_paymentLastname
| Last name at billing address step
|-valign="top"
| field_paymentCompany
| Company at billing address step
|-valign="top"
| field_paymentStreet
| Street at billing address step
|-valign="top"
| field_paymentStreet2
| Additional part for street at billing address step
|-valign="top"
| field_paymentZipCode
| Zip code at billing address step
|-valign="top"
| field_paymentCity
| City at billing address step
|-valign="top"
| field_paymentState
| US State at billing address step (use two digit state code from [https://en.wikipedia.org/wiki/ISO_3166-2:US ISO 3166-2:US])
|-valign="top"
| field_paymentCountry
| Country at billing address step (use [https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO 3166-1 alpha-2] country codes)
|-valign="top"
| field_paymentEmail
| Email address at billing address step
|-valign="top"
| field_paymentTelephone
| Telephone number at billing address step
|-valign="top"
| field_paymentReferenceNo
| Reference number at billing address step
|-valign="top"
| field_paymentVatId
| VAT-ID at billing address step
|-
| colspan="2" | '''Custom fields at billing address step:''' (see below table for more details) 
|-valign="top"
| field_payment_<field_id>
| Set a value for a custom field you added to the billig address step
|-
| colspan="2" | '''Shipment address:''' 
|-valign="top"
| field_shipmentFirstname
| First name of shipment address
|-valign="top"
| field_shipmentLastname
| Last name of shipment address
|-valign="top"
| field_shipmentCompany
| Company of shipment address
|-valign="top"
| field_shipmentStreet
| Street of shipment address
|-valign="top"
| field_shipmentStreet2
| Additional part for street of shipment address
|-valign="top"
| field_shipmentZipCode
| Zip code of shipment address
|-valign="top"
| field_shipmentCity
| City of shipment address
|-valign="top"
| field_shipmentState
| US State of shipment address (use two digit state code from [https://en.wikipedia.org/wiki/ISO_3166-2:US ISO 3166-2:US])
|-valign="top"
| field_shipmentCountry
| Country of shipment address (use [https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 ISO 3166-1 alpha-2] country codes)
|-
| colspan="2" | '''Standard fields at ticket data step:''' replace <nowiki><i></nowiki> with the ticket number (e.g. field_ticket1Email, field_ticket2Email)
|-valign="top"
| field_ticket<i>Salutation
| Salutation of attendee (0=Mr, 1=Ms., 2=Mrs.)
|-valign="top"
| field_ticket<i>Title
| Title of attendee (Dr., Prof., ...)
|-valign="top"
| field_ticket<i>Firstname
| First name of attendee
|-valign="top"
| field_ticket<i>Lastname
| Last name of attendee
|-valign="top"
| field_ticket<i>Company
| Company of attendee
|-valign="top"
| field_ticket<i>Email
| Email of attendee
|-
| colspan="2" | '''Custom fields at ticket data step:''' (see below table for more details) 
|-valign="top"
| field_ticket<i>_<field_id>
| Set a value for a custom field you added to the billig address step

|}

To set values for the cstom fields you added to the ticket shop (e.g. text boxes, checkboxes, etc.) you need to get the internal ID of that field to set the value in the URL.<br/>
You can retrieve the ID via our REST API [[REST_API_Events#Enumerate_userDataDefinitions|Enumerate userDataDefinitions]].<br>
* - Fields of type "date" need to be addressed in the format: yyyy-MM-dd'T'HH:mm:ss
* - Fields of type "gender" have the format: 0=male, 1=female
* - Fields of type "checkbox" expect 0 (unchecked) or 1 (checked)
* - Fields of type "dropdown" and "radio" expect our "key" for the desired item (see 'userDataOptionKey' in [[REST_API_UserDataDefinition#User_Data_Options|User Data Options]]
* - Fields of type "address" expect each element as a separate parameter (Street, Street2, ZipCode, City, State, Country), e.g. field_ticket1_19053051Street=street)

'''Additional notes:'''
* - Additional products can not be set with this approach
* - Always remember to URL encode your values