TeamApp Admin API

Use this skill for TeamApp admin operations against JSON endpoints discovered from the web app.

Quick Workflow

1. 1. Resolve IDs first.

• - Load references/api-map.md and fetch club_id, team_id, and access_level_id values from list endpoints.

1. 2. Read form schemas before writing.

• - Open new.json or edit.json endpoint for the target resource.
• Use the embedded onSubmit controller and URL as source of truth for method and endpoint.

1. 3. Create or update content.

• - Submit payload fields exactly as named in the schema.
• For visibility-scoped content, set ...access_level_ids_csv only when visibility is access_groups.

1. 4. Verify by reloading list endpoints.

• - Re-read list JSON and confirm returned object IDs, titles, and action URLs.

Auth and Session Requirements

MANDATORY: All interactions with the TeamApp API via this skill must use the provided wrapper script bin/api-wrapper.sh.

This wrapper automatically handles:

• - Session bootstrapping (fetching the dashboard to establish a session).
• CSRF token extraction and caching.
• Cookie management (ta_auth_token and _teamapp_session).
• Session refreshing on expiration (401/422 errors).

Required Environment Variables

The wrapper requires the following variables to be set in your shell environment:

• - TA_AUTH_TOKEN: The ta_auth_token cookie value (extracted from a browser session).

Usage

Call the wrapper with the HTTP method, the full URL, and any curl options (like data payloads).

CODEBLOCK0

Example: Read Articles
CODEBLOCK1

Example: Create Article
CODEBLOCK2

Scheduling and Notifications

All News and Events support scheduling and configurable notification delivery.

Scheduling (Release Control)

• - ...[release_pending]: Set to 0 for immediate release, or 1 to schedule for later.
• INLINECODE17: When release_pending is 1, provide an ISO 8601 timestamp (e.g., 2026-03-25 10:00).

Notification Delivery

The send_notifications parameter controls how users are alerted:

• - 0: None (Silent release)
• INLINECODE23: Push OR Email (Default: sends push if enabled on device, falls back to email if notifications are disabled)
• INLINECODE24: Push AND Email (Sends both regardless of app notification status)

Event Reminders

Events include an additional event[reminder] field for automated alerts:

• - -1: None
• INLINECODE27: At starting time
• INLINECODE28: 30 minutes before
• INLINECODE29: 1 hour before
• INLINECODE30: 1 day before (and other standard intervals in seconds)
• INLINECODE31: Custom (requires event[reminder_datetime])

Operations

News Articles (create/read/update)

• - Endpoint map and payload fields: see references/api-map.md.

Required baseline fields for create:

• - INLINECODE33
• INLINECODE34
• INLINECODE35 (public|approved_members|access_groups)
• INLINECODE37 (0|1)
• INLINECODE39 (0|1)
• INLINECODE41 (0|1)
• INLINECODE43 (0|1)
• INLINECODE45 (0|1|2)

Schedule Events (create/read/update)

• - Endpoint map and payload fields: see references/api-map.md.

Key fields:

• - event[team_id], INLINECODE48
• INLINECODE49, event[datetime_end] or all-day fields
• INLINECODE51 / html variant fields
• INLINECODE52, INLINECODE53
• INLINECODE54, INLINECODE55
• INLINECODE56, event[reminder], INLINECODE58

Teams and Access Groups (ID resolution + targeting)

Use list endpoints to resolve IDs before posting news/events:

• - Teams: see references/api-map.md.
• Access groups: see references/api-map.md.

Use team/access-group IDs in:

• - INLINECODE59
• INLINECODE60
• INLINECODE61
• INLINECODE62
• INLINECODE63

References

• - Endpoint and payload map: references/api-map.md