LLSR API - Member API Specification and Examples
Root Nodes
/member Member API root node
/member/lookup/{first-name}/{last-name}/{date-of-birth} Lookup the member ID of the specified
profile
/member/profile/{member-id} Query the member profile associated with the
specified member ID
/member/update/{first-name}/{last-name}/{date-of-birth} Update all info associated with the matching
member profile
/member/lookup/{first-name}/{last-name}/{date-of-birth}
Reading
Look up the member ID of the profile matching the specified first name, last name, and date of birth. Whitespace and other non alphanumeric characters should be URL encoded; e.g., the name "von Trier" would be represented as "von%20Trier". Date of birth should be specified using the format YYYY-MM-DD. The following example shows how the /member/lookup endpoint is used to achieve this:
GET /member/lookup/Lars/von%20Trier/1956-04-30 HTTP/1.1
Host: api.skilouise.com
In this example, a query on the lookup endpoint would generate the following JSON-encoded result:
{
"memberID":683156
}
If the matching member profile does not exist, the first name, last name, and date of birth search terms will be stored, and a corresponding temporary member ID prefixed with the latter 'e" returned; e.g.:
{
"memberID":e789
}
This temporary member ID can be used wherever a member ID is called for in the Waiver API. Visit the Waiver API documentation for more information.
Publishing
Unavailable.
Updating
Unavailable.
Deleting
Unavailable.
/member/profile/{member-id}
Reading
Query the member profile associated with the specific member ID. The following example shows how the /member/profile endpoint is used to achieve this:
GET /member/profile/823187 HTTP/1.1
Host: api.skilouise.com
In this example, a query on the lookup endpoint would generate the following JSON-encoded result:
{
"firstName":"TESTOPHER",
"middleInitial":"X",
"lastName":"TESTOFFERSON",
"sex":"M",
"birthDate":"1970-01-01",
"address1":"1 TESTLAAN",
"address2":"SUITE 1",
"city":"TESTDAM",
"province":"AB",
"country":"CANADA",
"postalCode":"N0N0N0",
"phonePrefix":"",
"phoneNumber":"555 555 5555",
"phoneExtension":"",
"emailAddress":"[email protected]"
}
If no profile exists for the given member ID, an error is returned; e.g.:
{
"error":{
"message":"Member profile not found"
}
}
Publishing
Unavailable.
Updating
Unavailable.
Deleting
Unavailable.
/member/update/{first-name}/{last-name}/{date-of-birth}
Reading
Unavailable.
Publishing
Unavailable.
Updating
Write values for all fields of the the member matching the specified first name, last name, and date of birth. Whitespace and other non alphanumeric characters should be URL encoded; e.g., the name "von Trier" would be represented as "von%20Trier". Date of birth should be specified using the format YYYY-MM-DD. The following example shows how the /member/update endpoint is used to achieve this:
POST /member/update/Hunter/Thompson/1937-07-18 HTTP/1.1
Host: api.skilouise.com
firstName=Hunter&middleInitial=S&lastName=Thompson&sex=M&dateOfBirth=1937-07-18
&address1=The Strip&address2=&city=Las Vegas&province=NV&country=USA&postalCode=89109
[email protected]&mailConsent=False&emailConsent=False
In this example, a query on the update endpoint might generate the following JSON-encoded result:
{
"memberID":123456,
"created":false
}
If the matching member profile does not exist, a new member profile is created with the given profile info; e.g.:
{
"memberID":999999,
"created":true
}
Deleting
Unavailable.
HTTP Status Codes
The Scanning API uses the following standard HTTP status codes:
200: OK
400: Bad Request
401: Unauthorized
503: Service Unavailable