> For the complete documentation index, see [llms.txt](https://docs.mymedtrics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mymedtrics.com/api-reference/graphql-gateway/lti-platforms.md).

# LTI platforms

The LMS platforms registered for your institution, their courses and grade links.

The LMS platforms registered for your institution, their courses and grade links. 4 queries; send any of them to the endpoint on the [GraphQL gateway](/api-reference/graphql-gateway.md) page, the same way as the first query there.

### ltiPlatforms

The LTI 1.3 platforms registered for an institution.

Arguments: **`institutionId`** (ID, required)

```graphql
query {
  ltiPlatforms(institutionId: "…") { id institutionId name issuer deploymentId }
}
```

Returns `[LTIPlatform!]!`:

#### LTIPlatform

| Field           | Type       |
| --------------- | ---------- |
| `id`            | `ID!`      |
| `institutionId` | `ID!`      |
| `name`          | `String!`  |
| `issuer`        | `String!`  |
| `deploymentId`  | `String`   |
| `isActive`      | `Boolean!` |
| `lastSyncAt`    | `String`   |
| `lastError`     | `String`   |
| `createdAt`     | `String!`  |
| `updatedAt`     | `String!`  |

### ltiPlatform

One registered platform by id.

Arguments: **`id`** (ID, required)

```graphql
query {
  ltiPlatform(id: "…") { id institutionId name issuer deploymentId }
}
```

Returns `LTIPlatform` — fields as under [LTIPlatform](#ltiplatform) above.

### ltiContexts

The LMS courses (contexts) seen through a platform.

Arguments: **`platformId`** (ID, required)

```graphql
query {
  ltiContexts(platformId: "…") { id platformId contextId label title }
}
```

Returns `[LTIContext!]!`:

#### LTIContext

| Field            | Type      |
| ---------------- | --------- |
| `id`             | `ID!`     |
| `platformId`     | `ID!`     |
| `contextId`      | `String!` |
| `label`          | `String`  |
| `title`          | `String`  |
| `courseId`       | `ID`      |
| `lastActivityAt` | `String`  |
| `createdAt`      | `String!` |

### ltiGradeLinks

The gradebook line items linked under a context.

Arguments: **`contextId`** (ID, required)

```graphql
query {
  ltiGradeLinks(contextId: "…") { id contextId resourceLinkId lineItemUrl courseId }
}
```

Returns `[LTIGradeLink!]!`:

#### LTIGradeLink

| Field                | Type         |
| -------------------- | ------------ |
| `id`                 | `ID!`        |
| `contextId`          | `ID!`        |
| `resourceLinkId`     | `String!`    |
| `lineItemUrl`        | `String!`    |
| `courseId`           | `ID`         |
| `scoreTypeId`        | `ID`         |
| `isActive`           | `Boolean!`   |
| `syncEnabled`        | `Boolean!`   |
| `syncState`          | `String!`    |
| `deliveryGeneration` | `Int!`       |
| `lastSyncAt`         | `String`     |
| `syncDirection`      | `String!`    |
| `lastSyncStatus`     | `SyncStatus` |
| `lastError`          | `String`     |
| `createdAt`          | `String!`    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mymedtrics.com/api-reference/graphql-gateway/lti-platforms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.