Trainer Command Center API

Give people access to your team plans from your own CRM, checkout or automation tool, and get notified when your team changes. Built for CRMs, checkouts and no-code automation tools such as GoHighLevel and Zapier.

With the API you can:

• Add a person to one or more of your team plans, creating their account if they don't have one yet.
• Remove a person from one plan, or from all of your plans at once.
• Look up your team plans and the people on them.
• Receive a webhook when someone joins or leaves a plan, or when a plan is created, changed or deleted.

Each trainer has their own API key, and a key only ever sees that trainer's own team plans and the people on them.

Quickstart

1. Get your API key Sign in to Trainer Command Center, open your Profile, and under Zapier API key click Generate Api Key, then Copy Api Key. The same key works for direct API calls and for our Zapier app (the Zapier app is invite-only; see Zapier).
2. Check the key works
   Copy

   export TCC_API_KEY="paste-your-key-here"
   export TCC_API="https://us-central1-trainer-command-center-prod.cloudfunctions.net/zapier_tcc_app_connector"
   
   curl "$TCC_API/whoami" -H "Authorization: Bearer $TCC_API_KEY"

   A 200 with your email means you're connected. A 403 means the key is wrong; copy it again from your Profile.
3. Find the team plan you want to grant
   Copy

   curl "$TCC_API/team-plan" -H "Authorization: Bearer $TCC_API_KEY"

   This lists every plan you own. Note the id of the one you want.
4. Add someone to it
   Copy

   curl -X POST "$TCC_API/upsert-user" \
     -H "Authorization: Bearer $TCC_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"email":"jordan@example.com","firstName":"Jordan","lastName":"Reyes","teamPlanIds":["YOUR_TEAM_PLAN_ID"]}'

   If Jordan already has an account, the plan is added to it. If not, an account is created with the plan on it and Jordan is emailed an invitation to set up their login. Either way you get Jordan's record back. This is the live system, so test with your own email address or a teammate's, then remove the plan again with /remove-team-plan-from-user.

Authentication

Send your API key in the Authorization header on every request. Both of these forms work:

Authorization: Bearer YOUR_API_KEY
Authorization: YOUR_API_KEY

A request with no key, an unknown key or a disabled key gets 403 with the body Unauthorized. The response is the same in all three cases.

What a key can see

A standard key has access level OWN_TEAM_PLANS. It can only grant, remove and list plans you own, and it can only look up people who are on one of your plans. Through the endpoints, plans belonging to other trainers are treated as if they don't exist.

Sending requests

Read requests use query parameters. Write requests are POST with a JSON object as the body. The body can be sent as application/json or as JSON text with text/plain, so most no-code tools work without extra configuration.

Fields in write requests

Every write endpoint reads the same four fields. Each one can be spelled in camelCase or snake_case:

Team plan ids

You can send teamPlanIds in whichever form your tool can produce. All of these mean the same thing:

{ "teamPlanIds": ["PLAN_ID_A", "PLAN_ID_B"] }     // JSON array
{ "teamPlanIds": "PLAN_ID_A,PLAN_ID_B" }        // comma-separated text
{ "team_plan_id": "PLAN_ID_A" }                 // a single id

Ids can also be separated by line breaks. Duplicates are ignored.

Fields nested under customData

If your tool wraps your fields in a customData object (GoHighLevel workflow webhooks do this), the API looks there too. A field at the top level takes priority over the same field inside customData.

Responses and errors

Successful responses are JSON. Error responses are plain text that says what went wrong, for example Failed to add team plan to user. User with email jordan@example.com does not exist.

Grant and remove requests are safe to retry. Granting one of your active plans to someone who already holds it, or removing one they don't hold, changes nothing and still returns 200. POST /user is the exception: a retry after a successful create returns 400 because the account now exists.

Webhooks

Webhooks tell your system when something changes on your team, whether the change came through the API or someone made it in Trainer Command Center. Register a URL for each event you care about.

{
  "hookUrl": "https://your-system.example.com/tcc-events/9f3c1a",
  "triggerKey": "team_plan_added"
}

{ "hookId": "Hk2nW5qZr8Lt1VcPy7Ms" }

curl -X DELETE "$TCC_API/zapier-hook/Hk2nW5qZr8Lt1VcPy7Ms" -H "Authorization: Bearer $TCC_API_KEY"

Events

Use these values as triggerKey. You only receive events for team plans you own.

Member change payload

{
  "id": "Uv6mB0yQe3Js8FhK2wTa",
  "email": "jordan@example.com",
  "firstName": "Jordan",
  "lastName": "Reyes",
  "teamPlanId": "Pz4cW7nLq2Rk9TbXv1Hs",
  "teamPlanLevel": "Stack"
}

teamPlanLevel is the display name of the plan's level. A change that adds or removes several plans at once sends one event per plan.

Person payload

{
  "id": "Uv6mB0yQe3Js8FhK2wTa",
  "email": "jordan@example.com",
  "firstName": "Jordan",
  "lastName": "Reyes",
  "activeTeamPlanIds": ["Pz4cW7nLq2Rk9TbXv1Hs"]
}

activeTeamPlanIds lists the person's active team plans at the time of the event.

Courses payload

{
  "id": "Uv6mB0yQe3Js8FhK2wTa",
  "email": "jordan@example.com",
  "firstName": "Jordan",
  "lastName": "Reyes",
  "accessToWarriorCoursesHasBeenGranted": true
}

Team plan payload

{
  "id": "Pz4cW7nLq2Rk9TbXv1Hs",
  "name": "Inner Circle",
  "teamPlanLevel": "Stack",
  "status": "active",
  "permissions": [],
  "noCost": false,
  "createdAt": 1727712000000,
  "ownerId": "Kq81ZtR3VwLm5xPa0dNc",
  "ownerEmail": "coach@example.com",
  "ownerFirstName": "Sam",
  "ownerLastName": "Carter",
  "includeWarriorCourses": true
}

status is active, deactivated or deleted. A deactivated plan stops granting access until it is active again; this happens, for example, when a plan's billing is overdue.

Plan change payload

The plan as it was and as it is now, each in the team plan shape. before is left out when the plan has just been created.

{
  "id": "Pz4cW7nLq2Rk9TbXv1Hs",
  "before": { "name": "Inner Circle", "status": "active", … },
  "after":  { "name": "Inner Circle 2026", "status": "active", … }
}

Delivery

• Each event is sent as an HTTP POST whose body is JSON text. The Content-Type header is text/plain, so parse the raw body as JSON rather than relying on the header.
• Each event is sent once, and the status code your endpoint returns isn't checked. Failed deliveries are not retried, so if missing an event matters, check the person with GET /user when your system next acts on them.
• Requests are not signed. Use a long, hard-to-guess URL for your endpoint, and treat the payload as a prompt to look up current state rather than as the final word.
• Events are sent shortly after the change, and they aren't guaranteed to arrive in order.

GoHighLevel

To give someone access when they buy, book or get tagged in GoHighLevel:

1. In your workflow, add a webhook action that lets you set request headers (in GoHighLevel this is the Custom Webhook action).
2. Set the method to POST and the URL to https://us-central1-trainer-command-center-prod.cloudfunctions.net/zapier_tcc_app_connector/upsert-user.
3. Add the header Authorization with the value Bearer YOUR_API_KEY.
4. In the body, send email, first_name and last_name from the contact, and team_plan_ids with your plan id. To grant several plans, separate the ids with commas. Your plan ids come from GET /team-plan; if you can't run that call yourself, ask support for the ids of your plans.

GoHighLevel's own field names (first_name, contact_email), its customData wrapper and its habit of sending lists as text are all understood, so you can map contact fields directly. To take access away, point a second workflow at /remove-team-plan-from-user with the same body. This works while the plan is active; see deactivated plans.

Zapier

Our Zapier app uses this same API and the same key. When you connect it with your key, its actions (add user, which calls /upsert-user; add or remove a team plan; remove all team plans), its searches (find a user, find a team plan) and its triggers map one-to-one onto the endpoints and events on this page. You can mix the two: for example, receive events in Zapier and make calls from your own system.

Your API key

• Each trainer account has one key. Generate it from your Profile in Trainer Command Center; once generated, the same key is shown there for you to copy again.
• Your key belongs to your account. Anyone holding it can act on your team plans, so share it only with tools and people you trust with that.
• To replace a key that may have leaked, or to request broader access for a support or agency setup, contact the Trainer Command Center support team. Replacing a key disconnects every tool that uses the old one, including webhook registrations, so plan to reconnect them.