This PriceTravel’s API enables you to quote, create and get reservations; also you can cancel existing reservations. This API is a REST based Web Services
Using this API requires familiarity with the following REST Architecture concepts:
A resource is anything that can be represented by a set of bits stored in a computer. Such as a document, a database record, the result of an algorithm. The API is structured based on a set of resources.
Resources must respond to one or more of the HTTP standard methods: GET, POST, PUT, DELETE, and OPTIONS.
Use of the standard HTTP headers to specify request and response information.
The operation result is returned as a HTTP response code.
The XML tags and the JSON object field names will be written in UpperCamelCase. This is, the first letter for each word will be upper case and the rest in lower case, no underscores, dashes or spaces are allowed between the words.
Examples:HotelInformation, CountryCode, ServiceCharge, etc.The resource URI’s are expressed in plural and lowercase.
Examples:https://api.pricetravel.com/services/hotelsAll URI segments found between curly brackets, like {hotelId}, must be substituted by the desired values. And the segments between square brackets, like [/{hotelId}], are optional.
The supported format for date and time elements is ISO 8601 (http://en.wikipedia.org/wiki/ISO_8601).
Dates are specified as YYYY-MM-DD.
Date and time is specified as YYYY-MM-DDThh:mm.
Where:
We use the IETF language tag (http://en.wikipedia.org/wiki/IETF_language_tag). For example: en for English, en-US for United States English, es for Spanish, es-MX for Mexican Spanish.
The currency format is the standard ISO 4217 (http://es.wikipedia.org/wiki/ISO_4217), it uses three letter codes. For example: USD for US dollars, MXN for Mexican pesos and GBP for Great Britain pounds.
The country code format is ISO 3166-1, Alpha-2 (http://es.wikipedia.org/wiki/ISO_3166-1). It uses two letter codes. For example: US for United States, MX for Mexico and GB for Great Britain.
For the test environment the URI must be preceded by the stage prefix.
For example the URI:
Must be changed to: