8. The extra_info method

Returns the extra information associated with the event.

Hint

Information can be requested using the “mime_text_type” input as described in the section on XML core basic calling conventions

8.1. Input

8.1.1. Required inputs

• “crypto_block” from “event_search”.
• “event_token” element.

8.1.2. Optional Input

• “source_info”

8.1.3. Example input

<extra_info>
    <user_id>demo</user_id>
    <crypto_block>M_--qRfq64CDfM9Vj4JBQdRMdOJPW0xEpX1WsPqJY6Sy_X--q
    -u7vOoeQH9kWHcDhhX0y1R6--Q5LYtL2zZeBLtUFtT8k2_EW3NjhoJBWdGhx6TV
    _mcqVl1vM---Y</crypto_block>
    <event_token>MQ2JX</event_token>
</extra_info>

8.2. Output data

• source_after_sales_email - The email address which should

  be used for after-sales customer services.

• source_card_statement_desc - The text which will appear

  on the customers credit card statement as the debitor for this event.

• source_enquiries_email - The email address for general

  enquiries regarding this supplier.

• source_local_phone - Details of how to telephone customer

  services for customers located in the suppliers country.

• source_local_fax - Details of how to send a fax to

  customer services for customers located in the suppliers country.

• source_international_phone - Details of how to telephone

  customer services for customers located outside the suppliers country.

• source_international_fax - Details of how to send a fax to

  customer services for customers located outside the suppliers country.

• source_postal_addr - The postal address for sending

  physical mail to customer services.

• source_t_and_c - The suppliers terms and conditions. This

  will usually be a long paragraph of legal text which should be made available to the customer in some way.

8.3. About Media Assets

To request the media assets which may be associated with an event a number of “request_media” elements may be included in the input, each containing the same of a media file to be returned if possible. For each available requested media asset, an “event_media” element will be present in the output Each of these will contain two sub-elements, one being “name” containing the name of the media file, and one being “data” which contains the data in hexadecimal form. At the time of writing the media assets which may be associated with an event include images called “square”, “landscape”, “triplet_one”, “triplet_two”, “triplet_three”, “triplet_four”, “triplet_five”, “marquee”, “seating_plan”.

Hint

• If the source information was requested using “source_info” then a number of extra elements may be present in the output.
• The terms and conditions element is always included

8.3.1. Example output

<extra_info_result>
<event_desc>Maria Pages</event_desc>
<venue_desc>Sadlers Wells</venue_desc>
<source_desc>Keith Prowse Ticketing</source_desc>
<source_code>fcg1</source_desc>
<country_code>uk</country_code>
<geo_data>
<latitude>51.52961137</latitude>
<longitude>-0.10601562</longitude>
</geo_data>
<venue_info>The world's No.1 venue dedicated to international
dance - presenting dance in all forms from contemporary to flamenco,
ballet to hip hop and more.

Nearest Underground: Angel (Northern line)
Nearest Rail: Kings Cross (Northern line to Angel)
Turn left out of Angel station and cross the road at the
crossroads for St John Street. Roseberry Avenue is on the right
with the theatre about 100 metres down on the right.</venue_info>
<venue_addr>Rosebery Avenue
Islington
London</venue_addr>
</extra_info_result>

8.4. Potential failure codes

• 1 - the supplied crypto block was not generated by

  “event_search”

• 2 - the requested “mime_text_type” was not a supported value
• 101 - no “event_token” has been supplied
• 102 - the supplied “event_token” is corrupt
• 103 - the event specified could not be found in the database