Use the Playpass API and playpass CLI to automate workflows with your AI agents and internal tools.

Common use cases include reading schedules, registrations, memberships, bookings, waivers, and website content, plus creating or updating organizer resources.

Using an AI agent like Codex, Claude Code, or OpenClaw? Share this guide link and tell the agent exactly what you want to build or automate.

Authentication setup

Most manager automation starts with an API token.

1. Create a token from Dashboard > Settings > API Access
2. Send the token as a bearer token with each request
3. Use the full plaintext token shown right after creation. The token name and the last four characters shown later will not authenticate.

Authorization: Bearer <your_plaintext_api_token>
X-Playpass-Api-Version: 2026-02-08

Manager API tokens are organizer-scoped and best for server-side or agent workflows.
Each token is limited to the creating user's permissions for that organizer and
still respects organizer pricing-plan limits.

If you open /api/... URLs directly in your browser, or your tool sends anything
other than the full plaintext token, Playpass will return 401.

With PLAYPASS_API_TOKEN set to the full plaintext token:

curl "https://playpass.com/api/schedules?organizer_id=<your_organizer_slug>" \
  --oauth2-bearer "$PLAYPASS_API_TOKEN" \
  -H "X-Playpass-Api-Version: 2026-02-08"

If you need player account authorization, use the OAuth endpoints in the same API reference.

Playpass CLI

The playpass CLI wraps the same public API and is useful for shell scripts, local testing, and AI-agent workflows.

Install the latest released CLI with the wrapper script:

curl -fsSL https://playpass.com/install.sh | sh

The installer automatically:

• Detects the current platform
• Downloads the latest published Playpass archive
• Verifies the archive against SHA256SUMS.txt
• Installs playpass into a writable bin directory

Today the published binaries support:

• macOS Apple Silicon (darwin-arm64)
• Linux x86_64 (linux-amd64)

If you need a different install location, set PLAYPASS_INSTALL_DIR before running the script.

Use the same token and API version header defaults from above:

export PLAYPASS_API_TOKEN="<your_plaintext_api_token>"
export PLAYPASS_API_VERSION="2026-02-08"
export PLAYPASS_OUTPUT="table"

playpass schedules list --organizer-id <your_organizer_slug> --view current
playpass organizers show <your_organizer_slug>

If you need an endpoint that is not yet wrapped by a first-class command, use the raw passthrough commands:

playpass api get "/api/schedules?organizer_id=<your_organizer_slug>&view=current"

Full API reference

• Playpass API docs

What's next?

• Create an API token from Dashboard > Settings > API Access
• Install the playpass CLI with curl -fsSL https://playpass.com/install.sh | sh
• Review endpoints and request/response examples in the Playpass API docs