> 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/get-started/quickstart.md).

# Quickstart

Get a token and make your first Connect API call.

Public REST contract for Medtrics Connect partner integrations. Medtrics-API-Date selects the request contract. Rotation creates with 2026-10-27 require clinical\_schedule\_id and block\_id; previously accepted dates preserve optional placement references through compatibility handling.

### Base URL and headers

```
https://<client-name>.mymedtrics.com/connect/<resource>
Authorization: Bearer <access token>
Medtrics-API-Date: 2026-10-27
```

{% hint style="info" %}
Testing first? Use `https://sandbox.mymedtrics.com` with an `X-Medtrics-Sandbox-Key` header instead of a bearer token — see [Sandbox](/get-started/sandbox.md). Everything else is identical.
{% endhint %}

Get a token once per session with your API app's live client credentials:

```bash
curl -X POST "https://<client-name>.mymedtrics.com/connect/oauth/token" \
  -H "Medtrics-API-Date: 2026-10-27" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials&client_id=$MEDTRICS_CLIENT_ID&client_secret=$MEDTRICS_CLIENT_SECRET"
```

Credentials are created, rotated and revoked in the portal under `/integrations/connect-api`; the API starts at the token exchange.

### Next

* [Sandbox](/get-started/sandbox.md) — a shared tenant on demo data to try calls before touching live records
* [Conventions](/get-started/conventions.md) — idempotency, webhooks, rate limits, hosting
* [Admin workflows](/get-started/admin-workflows.md) — which calls do which job, with the scopes to grant
* [Connect API reference](/api-reference/connect-api.md) — every operation, grouped by resource
* [Postman](/get-started/postman.md) — the same calls, ready to run
* [Classic data mapping](/get-started/classic-data-mapping.md) — where each table and field lands in Oracle, if you are moving from Medtrics Classic


---

# 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/get-started/quickstart.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.