Agentivity API

<back to all web services

EventBookingsRequest

The following routes are available for this service:
GET/EventBookings
EventBookingsRequest Parameters:
NameParameterData TypeRequiredDescription
UserNamequerystringYesUserName in form of an email address
EventCodequerystringNoEvent code
SplitMultiplePassengersquerybooleanNoSplit multiple passengers
IncludeNotesquerybooleanNoInclude notes in the response
IncludeArrivalDeparturesquerybooleanNoInclude arrival departures
FormattingStylequeryintegerNoIndicate the required formatting: 0=None(Default), 1=Html, 2=Chart
ItinerarySegmentsToShowquerystringNoItinerary segments to show
PagingMetadata Parameters:
NameParameterData TypeRequiredDescription
OffsetquerystringNoStarting Record
LimitquerystringNoNumber of records to return (PageSize)
TotalRecordsquerystringNoTotal Number of Records in a Full Reponse (if no paging)
ResponseRecordsquerystringNoTotal Number of Records in this Reponse (on this page)
ItemResponse<TItem, TReport> Parameters:
NameParameterData TypeRequiredDescription
ResponseMetadataformResponseMetadataNo
ResponseReportformTReportNo
ResponseErrorformAgentivityErrorNo
ResponseMetadata Parameters:
NameParameterData TypeRequiredDescription
SuccessformboolNo
HasCacheformboolNo
HasPagingformboolNo
CacheMetadataformCacheMetadataNo
PagingMetadataformPagingMetadataNo
CacheMetadata Parameters:
NameParameterData TypeRequiredDescription
CachedAtformDateTimeNo
CacheExpiresAtformDateTimeNo
IsFromCacheformboolNo
AgentivityError Parameters:
NameParameterData TypeRequiredDescription
ErrorCodeformstringNo
MessageformstringNo
StatusCodeformstringNo
VerboseMessageformstringNo
EventBooking Parameters:
NameParameterData TypeRequiredDescription
RecordLocatorformstringNo
PNRCreationDateformDateTimeNo
PaxListformstringNo
PaxCountformintNo
InboundAirlineformstringNo
InboundFlightNumberformstringNo
InboundArrivalCityformstringNo
InboundArrivalDateformDateTime?No
InboundArrivalTimeformstringNo
OutboundAirlineformstringNo
OutboundFlightNumberformstringNo
OutboundDepartureCityformstringNo
OutboundDepartureDateformDateTime?No
OutboundDepartureTimeformstringNo
NotesformstringNo
EmailsformstringNo
MobileformstringNo
TotalTicketedValueformstringNo
AgentivityRefformintNo
ItineraryFormattedformstringNo
ItineraryformItinerarySegmentsCollectionNo
ItinerarySegment Parameters:
NameParameterData TypeRequiredDescription
SegmentTypeformstringNo
SegmentNbrformintNo
BoardPointformstringNo
OffPointformstringNo
OperatorCodeformstringNo
OperatorServiceformstringNo
SegmentStatusformstringNo
DepartureTimeFormattedformstringNo
ArrivalTimeFormattedformstringNo
ChangeOfDayFormattedformstringNo
ServiceCodeformstringNo
StartDateformstringNo
EndDateformstringNo
TicketNumberformstringNo
VendorLocatorsquerystringNoComma separated list of vendor locators
EquipmentCodeformstringNo
EquipmentformstringNo
Report<TItemResponse, TItem> Parameters:
NameParameterData TypeRequiredDescription
ItemformTItemNo

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET //EventBookings HTTP/1.1 
Host: api.agentivity.com 
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<AgentivityResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="schemas.agentivity.com/types">
  <ResponseMetadata>
    <Success>false</Success>
    <HasCache>false</HasCache>
    <HasPaging>false</HasPaging>
    <CacheMetadata>
      <IsFromCache>false</IsFromCache>
      <CachedAt>0001-01-01T00:00:00</CachedAt>
      <CacheExpiresAt>0001-01-01T00:00:00</CacheExpiresAt>
    </CacheMetadata>
    <PagingMetadata>
      <Limit>String</Limit>
      <Offset>String</Offset>
      <ResponseRecords>0</ResponseRecords>
      <TotalRecords>0</TotalRecords>
    </PagingMetadata>
  </ResponseMetadata>
  <ResponseReport>
    <Item>
      <RecordLocator>String</RecordLocator>
      <PNRCreationDate>0001-01-01T00:00:00</PNRCreationDate>
      <PaxList>String</PaxList>
      <PaxCount>0</PaxCount>
      <AgentivityRef>0</AgentivityRef>
      <ItineraryFormatted>String</ItineraryFormatted>
      <Itinerary>
        <ItinerarySegment>
          <ArrivalTimeFormatted>String</ArrivalTimeFormatted>
          <BoardPoint>String</BoardPoint>
          <ChangeOfDayFormatted>String</ChangeOfDayFormatted>
          <DepartureTimeFormatted>String</DepartureTimeFormatted>
          <EndDate>String</EndDate>
          <Equipment>String</Equipment>
          <EquipmentCode>String</EquipmentCode>
          <OffPoint>String</OffPoint>
          <OperatorCode>String</OperatorCode>
          <OperatorService>String</OperatorService>
          <SegmentNbr>0</SegmentNbr>
          <SegmentStatus>String</SegmentStatus>
          <SegmentType>String</SegmentType>
          <ServiceCode>String</ServiceCode>
          <StartDate>String</StartDate>
          <TicketNumber>String</TicketNumber>
          <VendorLocators>String</VendorLocators>
        </ItinerarySegment>
      </Itinerary>
      <InboundAirline>String</InboundAirline>
      <InboundFlightNumber>String</InboundFlightNumber>
      <InboundArrivalCity>String</InboundArrivalCity>
      <InboundArrivalDate>0001-01-01T00:00:00</InboundArrivalDate>
      <InboundArrivalTime>String</InboundArrivalTime>
      <OutboundAirline>String</OutboundAirline>
      <OutboundFlightNumber>String</OutboundFlightNumber>
      <OutboundDepartureCity>String</OutboundDepartureCity>
      <OutboundDepartureDate>0001-01-01T00:00:00</OutboundDepartureDate>
      <OutboundDepartureTime>String</OutboundDepartureTime>
      <Notes>String</Notes>
      <Emails>String</Emails>
      <Mobile>String</Mobile>
      <TotalTicketedValue>String</TotalTicketedValue>
    </Item>
  </ResponseReport>
  <ResponseError>
    <ErrorCode>String</ErrorCode>
    <Message>String</Message>
    <StatusCode>String</StatusCode>
    <VerboseMessage>String</VerboseMessage>
  </ResponseError>
</AgentivityResponse>