URL Format

Full feed

The URL for accessing the full feed will be in the following format:


        https://api.peakadventuretravel.com/Feed/FeedService.svc/<FeedType>/<Brand>/<Version>/<APIKey>

Component

Description

Required?

Possible values

Default value

Example value

FeedType

The kind of data being requested

Mandatory

Product
Availability
Itinerary
TripNote

Product

Brand

The Intrepid brand for which you request the feed

Mandatory

Intrepid
Peregrine

Intrepid

Version

The version number of the feed being requested

Optional

The latest version of the requested feed

APIKey (replacing UserToken)

The API Key assigned to you. This authenticates you and provides access to the data for which you are authorized

Mandatory

269E38DC-8G7B-5C82-B7FE-056EDDB5E729

Request by product code

You can request a subset of the data for one product code by adding the URL component “Individual” after the feed type, and appending the product code to the URL. For example:


        https://api.peakadventuretravel.com/Feed/FeedService.svc/<FeedType>/Individual/<Brand>/<Version>/<APIKey>/<ProductCode>

Retrieving next/previous year's versions

Additionally, you can retrieve the next or previous year's versions of a particular trip product.

If today’s date is within the validity period (validFrom and validTo) for the default version of the trip's Product data, then you would use /next to get next year’s version. E.g. if the default product’s validity was until Dec 31, 2024 (and today being 1 May, 2024), then /next would return the 2025 version. Conversely, if today’s date is earlier than the start of the validity period (validFrom) for the default version of the trip's Product data, then you would need to use /previous to get this year’s version. E.g. if the default product’s validity start date was Jan 1, 2025 (and today being 1 May, 2024), then /previous would return the 2024 version.


        https://api.peakadventuretravel.com/Feed/FeedService.svc/<FeedType>/Individual/<Brand>/<Version>/<APIKey>/<ProductCode>/<Season>

Component

Description

Required?

Possible values

Default value

Example value

Season

Specifies whether to retrieve the next or previous season's version of the product

Optional

next
previous

URL Examples

Please note these examples will not work as the APIKey is invalid. These examples are specific to the brand Intrepid Travel. To use these examples for our other brands please replace Intrepid with the relevant brand identifier.

Click here for the list of supported brands


            https://api.peakadventuretravel.com/Feed/FeedService.svc/<FeedType>/Individual/<Brand>/<Version>/<APIKey>/<ProductCode>

Product

Availability

All Products

https://api.peakadventuretravel.com/Feed/FeedService.svc/availability/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729

Individual Product

https://api.peakadventuretravel.com/Feed/FeedService.svc/availability/Individual/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729/ttsk

Trip notes

All Products

https://api.peakadventuretravel.com/Feed/FeedService.svc/tripnote/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729

Individual Product (Default Version)

https://api.peakadventuretravel.com/Feed/FeedService.svc/tripnote/Individual/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729/ttsk

Individual Product (Default Version) - Next Year

https://api.peakadventuretravel.com/Feed/FeedService.svc/tripnote/Individual/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729/ttsk/next

Individual Product (Default Version) - Previous Year

https://api.peakadventuretravel.com/Feed/FeedService.svc/tripnote/Individual/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729/ttsk/previous

Itinerary

All Products

https://api.peakadventuretravel.com/Feed/FeedService.svc/itinerary/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729

Individual Product

https://api.peakadventuretravel.com/Feed/FeedService.svc/itinerary/Individual/Intrepid/269E38DC-8G7B-5C82-B7FE-056EDDB5E729/ttsk

Authentication and Security

Requests are authenticated by the APIKey component of the URL. An APIKey will be provided to you by your contact at Intrepid.

Secure requests can be made by prefixing the URL with https. In the current version, requests can be made without SSL as the information that constitutes the currently available feeds is not considered sensitive, however we would prefer that you always use SSL. In future, feed requests will only be allowed over an SSL connection.