Quick Start

This is the shortest path from "credentials in hand" to "I made a real call". Five minutes if your network and credentials are good.

What you need before starting

A client_id and client_secret issued by flaik. Don't have one? Contact resortsupport@flaik.com.
The API base URL Flaik gave you for your environment (something like https://api.flaik.com).
A way to make HTTPS requests — curl, Postman, your language's HTTP client, etc.

Step 1 — Fetch an access token

Send client_credentials to the token endpoint with the read scope:

curl -X POST https://auth-usw2.flaik.com/connect/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "scope=flaik.connect.api.read"

Expected response:

{
  "access_token": "eyJhbGciOiJSUzI1NiIs…",
  "expires_in": 3600,
  "token_type": "Bearer",
  "scope": "flaik.connect.api.read"
}

Copy the access_token value — you'll use it on every subsequent call.

Token expires after 1 hour. Cache and reuse it; fetch a new one when it's about to expire. See Authentication → Token Caching for the recommended pattern.

Step 2 — Confirm your tenant

Hit the resort details endpoint to confirm the token resolves to the resort you expect:

curl https://api.flaik.com/api/globalsettings/resort \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Expected response (truncated):

{
  "id": 42,
  "name": "Example Mountain Resort",
  "location": "Example, CO",
  "timezone": "America/Denver",
  ...
}

If the name and location match your resort — auth is wired up correctly. If you see a different resort, double-check the credentials. If you get a 401, the token is missing or invalid; fetch a new one.

See the full response shape on the Resort Details page.

Step 3 — List the resort's seasons

Most other endpoints take a seasonId. Get the list of available seasons next:

curl https://api.flaik.com/api/globalsettings/seasons \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Expected response (truncated):

[
  {
    "id": 17,
    "startDate": "2024-11-15",
    "endDate": "2025-04-30",
    "isCurrent": true,
    "nameLong": "Winter 2024–2025",
    ...
  },
  ...
]

The season with "isCurrent": true is the one happening now. Note the id — you'll pass it as {seasonId} on most other endpoints.

See the full response shape on the Seasons page.

Step 4 — Make a real data call

Use the season id from the previous step to fetch employee shifts for the current season:

curl https://api.flaik.com/api/schedule/shifts/17 \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"

Expected response shape:

{
  "data": [
    {
      "shiftId": 1042,
      "employeeId": 15,
      "scheduledDate": "2025-01-15",
      ...
    }
  ],
  "hasMore": true,
  "pageSize": 1000,
  "nextAfterId": 1042
}