AIM Web Services

<back to all web services

StationReservationRequest

StationReservation
Requires active-e Station Reservations Service

The following routes are available for this service:
POST/api/StationReservation
StationReservationRequest Parameters:
NameParameterData TypeRequiredDescription
StationIdqueryintegerYesThe ID of the station being reserved
AcctqueryintegerNoThe Customer Acct assosicated with the reservation. Either this or CustomerInfo is required.
CustomerInfoqueryobjectNo
CcInfoqueryobjectNo
StartquerystringYesThe start date/time of the reservation.
LengthqueryintegerYesThe length (in minutes) of the reservation.
GuestsqueryintegerNoNumber of guests (in addition to the customer) included in this reservation. Defaults to 0.
NotesquerystringNoNotes
BaseSecureRequest Parameters:
NameParameterData TypeRequiredDescription
TokenHeaderstringNoThe Login Token return by the Security API. Required for secured calls.
BaseRequest Parameters:
NameParameterData TypeRequiredDescription
ApiKeyHeaderstringYesThis is your AIM API Key provided by Tri-Tech
OAuthTokenHeaderstringYesThe OAuthToken token return by AeServices30
DeviceIdHeaderstringNoThe Device ID of the Mobile Device. Not used for non-mobile devices.
AppIdHeaderstringYesAn identifier for your integration
CustomerInfo Parameters:
NameParameterData TypeRequiredDescription
WebIdbodyintegerNoThe WebId of the customer. Optional.
NamebodystringYesName of the customer.
Addr1bodystringNoAddress line 1 of the customer
Addr2bodystringNoAddress line 2 of the customer
CitybodystringNoCity of the customer
StbodystringNoState/Province of the customer
ZipbodystringNoZip code of the customer
CountrybodystringNoCountry of the customer
PhonebodystringNoPhone number of the customer
EmailbodystringYesEmail address of the customer. Required.
CcInfo Parameters:
NameParameterData TypeRequiredDescription
TokenStrbodystringYesToken returned from processor
CardTypebodystringYesCard Type (VISA, MCARD, AMEX, DSCVR)
LastFourbodystringYesLast four of the card
ExpirationbodystringNoExpiration Date of the Card. (MM/YY)
ReasonOnFilebodystringNoReason the card is on file.
TokenPkbodyintegerNoID of the existing Token Record in AIM, if applicable
PrimarybodybooleanNoIs this the customer's primary card? Defaults to false.
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
StatusbodyBaseResponseResultNo
BaseResponseResult Parameters:
NameParameterData TypeRequiredDescription
StatusCodebodystringNo
LoginbodystringNo
ErrorCodebodystringNo
ErrorDisplayTextbodystringNo
ErrorMessagebodystringNo
DomainNamebodystringNo
IpAddressbodystringNo

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

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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

POST /api/StationReservation HTTP/1.1 
Host: active-ewebservice.biz 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"StationId":0,"Acct":0,"CustomerInfo":{"WebId":0,"Name":"String","Addr1":"String","Addr2":"String","City":"String","St":"String","Zip":"String","Country":"String","Phone":"String","Email":"String"},"CcInfo":{"TokenStr":"String","CardType":"String","LastFour":"String","Expiration":"String","ReasonOnFile":"String","TokenPk":0,"Primary":false},"Length":0,"Guests":0,"Notes":"String","Token":"String","ApiKey":"String","OAuthToken":"String","DeviceId":"String","AppId":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Status":{"StatusCode":"String","Login":"String","ErrorCode":"String","ErrorDisplayText":"String","ErrorMessage":"String","DomainName":"String","IpAddress":"String"}}