Data model

Every object shares these fields, so they're not repeated in the tables below:

In the tables, required means you must send the field when you create the item.

users are the people in your company. A person has a different user ID in each company they belong to.

teams are the teams in your company. isLeadership is true for the Leadership Team. A team's people are in usersOnTeams, a linking list with one record per person per team:

query {
  teams(filter: { stateId: { equalTo: "ACTIVE" } }) {
    nodes {
      id
      name
      isLeadership
      usersOnTeams(filter: { stateId: { equalTo: "ACTIVE" } }) {
        nodes { user { id firstName lastName } }
      }
    }
  }
}

To add someone to a team, create a usersOnTeam with their userId, the teamId and your companyId. To take them off, set its stateId to DELETED.

todos are 7-day action items, each owned by one person on one team.

Follow team, user, todoStatus and meeting for the related items.

issues are the Issues List: things to discuss and solve (IDS™).

Issue IDs are strings rather than UUIDs, so use String! for them in variables.

rocks are 90-day priorities.

A Rock can be shared with several teams, so it has no teamId. The link is in teamsOnRocks, with one record per team per Rock. To get one team's Rocks, look up the Rock IDs first:

query TeamRocks($teamId: UUID!) {
  teamsOnRocks(filter: { teamId: { equalTo: $teamId }, stateId: { equalTo: "ACTIVE" } }) {
    nodes { rockId }
  }
}

Then fetch those Rocks, with their Milestones:

query RocksById($ids: [UUID!]) {
  rocks(
    filter: { id: { in: $ids }, stateId: { equalTo: "ACTIVE" }, isArchived: { equalTo: false } }
    orderBy: DUE_DATE_ASC
  ) {
    nodes {
      id
      name
      dueDate
      rockStatus { name }
      user { firstName lastName }
      milestones(filter: { stateId: { equalTo: "ACTIVE" } }, orderBy: DUE_DATE_ASC) {
        nodes { name dueDate milestoneStatusId }
      }
    }
  }
}

When you create a Rock, create its teamsOnRock link in the same request, or it won't appear on any team. Creating and updating data has the full example.

milestones are the steps of a Rock. Each has a rockId, name, dueDate, userId and milestoneStatusId (TODO or COMPLETE). rockId, dueDate and userId are required.

headlines are the good news and updates shared in meetings.

A Scorecard is made of two objects:

• Measurables (dataFields) are the rows: the number, who owns it and its goal.
• Values (dataValues) are the cells: one number per measurable per period.

Like Rocks, measurables can be on several teams. The link is in teamsOnDataFields, with a teamId and a dataFieldId.

startDate must be the exact start of the measurable's period, or the value is refused:

There's one value per measurable per period. To change a number that's already there, update it rather than creating another. Recipes shows the full pattern.

Meetings come in two parts:

• meetingInfos are the recurring meetings you set up, such as a team's weekly Level 10 Meeting™. Each has a name, a teamId, an ownerUserId and the agenda it follows (meetingAgenda).
• meetings are each time it takes place, with its date, meetingInfoId, meetingStatusId (NOT-STARTED, STARTED, PAUSED or FINISHED), startTime, endTime and averageRating.

To-dos, Issues and Headlines raised in a meeting carry its meetingId, so you can list what came out of one:

query MeetingOutcomes($meetingId: UUID!) {
  meeting(id: $meetingId) {
    date
    averageRating
    todos(filter: { stateId: { equalTo: "ACTIVE" } }) { nodes { name user { firstName } } }
    issues(filter: { stateId: { equalTo: "ACTIVE" } }) { nodes { name issueStatusId } }
  }
}

comments are the comments on Rocks, To-dos, Issues, Headlines, Scorecard measurables and processes. Each has:

• objectId: the ID of the item it's on.
• type: what kind of item that is: rocks, todos, issues, headlines, dataFields (Scorecard measurables) or processes.
• text: the comment, as HTML.
• userId: who wrote it.

To get the comments on an Issue:

query IssueComments($issueId: String!) {
  comments(
    filter: { objectId: { equalTo: $issueId }, type: { equalTo: "issues" }, stateId: { equalTo: "ACTIVE" } }
    orderBy: CREATED_AT_ASC
  ) {
    nodes { text createdAt user { firstName lastName } }
  }
}

To add one, create a comment with objectId, type, text, userId and companyId.

Statuses are short IDs. Their display names, as the app shows them, are in a list for each kind, such as rockStatuses { nodes { id name } }.

The API also covers the V/TO™ (visions and their entities), the Accountability Chart™ (accCharts, accChartSeats), processes, the People Analyzer™, SWOT items and more. These follow the same patterns, and their fields are listed in the full schema.