LLSR API - Waiver API Specification and Examples

Note that the methods in this API require authentication to use them. Visit the Authentication API for more information.

Overview

The Waiver API can be used to create LLSR waiver records that serve to (1) notify the Lake Louise Ski Resort (LLSR) of the completion of
an electronic waiver administered by a third party and (2) provide LLSR with a method of accessing the completed waiver through its own
systems.

In calling the Waiver API, it is assumed that the third party will provide the member ID previously issued by LLSR to generate the
corresponding waiver invitation.

Root Nodes

/waiver                                                      Waiver API root node
/waiver/members/{memberID}/activities/{activityID}/waiver    Waiver for the specified member and 
                                                              activity

/waiver/members/{memberID}/activities/{activityID}/waiver

Reading

You can't read a waiver using the Waiver API.

Publishing

Creating/inserting a new waiver record is achieved by publishing to the waiver for a given member and activity.

In the URI, memberID should match the member ID provided when the waiver was generated, while activityID is a descriptor of the waiver activity composed of alphanumeric, hyphen (-), and underscore (_) characters.

This node takes four POST variables: signed, uniqueID, url, and photoURL.

signed represents the date and time the waiver was completed, in ISO 8601 standard format; e.g., midnight of January 1, 1970, in Mountain Time (GMT -7 hours) would be represented as: 1970-01-01T00:00:00-07:00

For uniqueID, any identifier can be specified (up to a maximum of 255 characters), and is merely intended to provide a meaningful reference to the requesting application's underlying data structures.

The provided url should locate a web-accessible copy of the waiver (maximum of 2083 characters).

Optional: a photoURL can be provided that should locate a web-accessible copy of the participant's photo (maximum of 2083 characters). The file encoding must be JPEG.

Example

POST /waiver/members/123456/activities/SEASON-PASS-18/waiver HTTP/1.1
Host: api.skilouise.com

signed=1970-01-01T00:00:00-07:00&uniqueID=TEST&url=https://ewaiver.example.com/TEST.pdf
&photoURL=https://ewaiver.example.com/TEST.jpg

The response will contain a success value of either true or false, depending on the outcome of the action, e.g.:

{
  "success":"true"
}

Updating

You can't update a waiver using the Waiver API.

Deleting

You can't delete a waiver using the Waiver API.

HTTP Status Codes

The Payment API uses the following standard HTTP status codes:

200: OK
400: Bad Request
401: Unauthorized
503: Service Unavailable