Organizations

Organizations let partners manage teams of athletes under a single billing structure. This is designed for coaching platforms, team managers, and enterprise partners who onboard athletes in groups. The examples read your key from a SATURDAY_API_KEY environment variable, as in Quickstart. Sandbox keys are issued with their own base URL; using one against api.saturday.fit returns 401 invalid_api_key.

Creating an organization

import os
import requests

response = requests.post(
    "https://api.saturday.fit/v1/organizations",
    headers={"Authorization": f"Bearer {os.environ['SATURDAY_API_KEY']}"},
    json={
        "display_name": "Seattle Running Club",
        "description": "Marathon training group",
        "sport": "run",
    },
)

org = response.json()  # 201 Created
org_id = org["id"]

const response = await fetch("https://api.saturday.fit/v1/organizations", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SATURDAY_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    display_name: "Seattle Running Club",
    description: "Marathon training group",
    sport: "run",
  }),
});

const org = await response.json(); // 201 Created
const orgId = org.id;

Field	Required	Description
`display_name`	Yes	Human-readable organization name
`description`	No	Free text
`sport`	No	Primary sport (e.g. `run`, `bike`, `triathlon`)

The response includes server-set id, created_at, updated_at, and a maintained member_count.

Managing members

Members are the organization’s people directory: coaches and staff, keyed by email. They are separate from athlete records, and linking a member row to an athlete via athlete_id is optional.

Adding members

import requests
import os

response = requests.post(
    f"https://api.saturday.fit/v1/organizations/{org_id}/members",
    headers={"Authorization": f"Bearer {os.environ['SATURDAY_API_KEY']}"},
    json={
        "email": "coach@seattlerunclub.com",
        "role": "admin",
        "athlete_id": "a1b2c3d4-...",  # optional link to an athlete record
    },
)

const response = await fetch(
  `https://api.saturday.fit/v1/organizations/${orgId}/members`,
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.SATURDAY_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      email: "coach@seattlerunclub.com",
      role: "admin",
      athlete_id: "a1b2c3d4-...", // optional link to an athlete record
    }),
  }
);

Member roles

Role	Meaning
`admin`	Organization manager (coach, team admin)
`member`	Everyone else. Applied when `role` is omitted

Any other value returns 400.

Listing and removing members

GET /v1/organizations/{org_id}/members
DELETE /v1/organizations/{org_id}/members/{member_id}

Removing a member never deletes an athlete profile; it removes the directory entry and decrements member_count.

Seat subscriptions (team licensing)

A seat subscription is a block of paid seats the organization holds; assigning a license to an athlete grants them full-precision API responses while the subscription is active and in its date window. This is the lane for orgs that pay for their athletes’ access directly (vs. athletes paying at personal checkout).

Create a seat block

POST /v1/organizations/{org_id}/subscriptions

{
  "type": "team",
  "seats": 25,
  "start_date": 1765467600,
  "end_date": 1797003600
}

type is "team" or "enterprise"; dates are unix seconds (end_date optional). The response includes used_seats (starts at 0) and status. Manage with GET /v1/organizations/{org_id}/subscriptions and PATCH .../subscriptions/{sub_id} (update seats, status, end_date).

Assign licenses to athletes

POST /v1/organizations/{org_id}/subscriptions/{sub_id}/licenses

{
  "licenses": [
    { "athlete_id": "a1b2c3d4-...", "email": "rider@example.com", "name": "Sam Rider" }
  ]
}

athlete_id is required per license (email/name are display metadata); the seat limit is enforced. The licensed athlete’s next API call returns full precision. GET .../licenses lists assignments; DELETE .../licenses/{athlete_id} frees the seat (access degrades on the athlete’s next call).

Organization offers (negotiated discounts)

A coach or team admin can negotiate a discount their athletes receive at personal checkout, as in “Team Alpine athletes get 15% off Saturday.” You record it as the organization’s offer, and Saturday applies it automatically when an affiliated athlete follows a subscribe CTA from your app. Each organization has at most one active offer. PUT creates or replaces it. Previous offers are deactivated rather than deleted, so the document trail is the negotiation audit log.

Setting the offer

PUT /v1/organizations/{org_id}/offer

import requests
import os

response = requests.put(
    f"https://api.saturday.fit/v1/organizations/{org_id}/offer",
    headers={"Authorization": f"Bearer {os.environ['SATURDAY_API_KEY']}"},
    json={
        "discount_percent": 15,
        "applies_to_plan": "12_month",
        "negotiated_by": "Coach Dana Reyes",
        "note": "2026 season team agreement",
    },
)

const response = await fetch(
  `https://api.saturday.fit/v1/organizations/${orgId}/offer`,
  {
    method: "PUT",
    headers: {
      Authorization: `Bearer ${process.env.SATURDAY_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      discount_percent: 15,
      applies_to_plan: "12_month",
      negotiated_by: "Coach Dana Reyes",
      note: "2026 season team agreement",
    }),
  }
);

Field	Required	Description
`discount_percent`	Yes	`1` to `30`. 30 is the stack cap (see below), and offers above it are rejected up front so you never promise athletes a number checkout won’t honor.
`applies_to_plan`	No	`"12_month"`, `"1_month"`, or omit to apply to all plans
`negotiated_by`	No	Human label for the audit trail, such as a coach name. Informational, not authentication
`starts_at` / `ends_at`	No	Unix seconds. Omit either for an open-ended window
`note`	No	Free text: why this discount exists

The response echoes the stored offer plus stack_cap_percent, the hard ceiling on the total stacked discount (currently 30).

Reading and removing the offer

GET /v1/organizations/{org_id}/offer      # current active offer; 404 when none
DELETE /v1/organizations/{org_id}/offer   # deactivates it; idempotent, returns 204

Which athletes get it

The offer applies to athletes whose org_id field references this organization. Assert it when creating or updating the athlete:

PATCH /v1/athletes/{athlete_id}

{
  "org_id": "5d8f3b21-7c04-4e19-9a6b-2f0c7e4d1a83"
}

org_id is partner-asserted, the same trust posture as partner_plan, and the organization must already exist: pointing at an org you have not created returns 400 rather than silently producing an athlete whose team discount never applies. A seat license is not required, since the discount is for the athlete’s own purchase and not a license entitlement. Set org_id to an empty string to remove the affiliation.

Stacking with partner offers

If your platform also has a partner-level offer (e.g. bundle pricing for your annual subscribers), eligible athletes get both: the percents combine multiplicatively, and the total is hard-capped at 30%. A 20% partner offer combined with a 15% org offer gives 1 - (0.80 × 0.85) = 32%, which the cap reduces to 30%. Checkout applies one combined discount, and Saturday’s subscribe landing page shows the stacked percent, the exact number the athlete will pay, along with which sources contributed. See Freemium Model, Bundle offers for the full discount flow.

Listing organizations

GET /v1/organizations

Returns all organizations created by your partner account.

Updating an organization

PATCH /v1/organizations/{org_id}

{
  "display_name": "Seattle Running Club - Elite Squad",
  "description": "Elite marathon squad"
}

Finding an organization’s athletes

Athletes reference their organization through the org_id field on the athlete record (POST /v1/athletes and PATCH /v1/athletes/{athlete_id}, see Organization offers above). There is no endpoint that lists an organization’s athletes. To build a team roster view, keep your own athlete-to-org mapping as you assert org_id, or for licensed teams use the seat-subscription license list: GET .../licenses returns exactly the athletes the org covers.

Getting Started

Core Guides

Integration Guides

Coach API

Platform

Organizations

Organizations

Creating an organization

Managing members

Adding members

Member roles

Listing and removing members

Seat subscriptions (team licensing)

Create a seat block

Assign licenses to athletes

Organization offers (negotiated discounts)

Setting the offer

Reading and removing the offer

Which athletes get it

Stacking with partner offers

Listing organizations

Updating an organization

Finding an organization’s athletes

​Organizations

​Creating an organization

​Managing members

​Adding members

​Member roles

​Listing and removing members

​Seat subscriptions (team licensing)

​Create a seat block

​Assign licenses to athletes

​Organization offers (negotiated discounts)

​Setting the offer

​Reading and removing the offer

​Which athletes get it

​Stacking with partner offers

​Listing organizations

​Updating an organization

​Finding an organization’s athletes

Organizations

Creating an organization

Managing members

Adding members

Member roles

Listing and removing members

Seat subscriptions (team licensing)

Create a seat block

Assign licenses to athletes

Organization offers (negotiated discounts)

Setting the offer

Reading and removing the offer

Which athletes get it

Stacking with partner offers

Listing organizations

Updating an organization

Finding an organization’s athletes