> ## Documentation Index
> Fetch the complete documentation index at: https://docs.medwrite.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Overview of the MedWrite API and authentication

The MedWrite API lets you integrate with clinical documentation, letters, and HL7 messaging. This reference covers authentication, Get Records endpoints, and the HL7 Receiver.

## Authentication

All API and embedded access is secured with industry-standard authentication. Access is controlled through **API keys** and **JWT bearer tokens** so only authorized systems and users can call the platform.

* Tokens are time-limited and signed with RS256.
* Each session is scoped to a specific organisation; users can only access data for their authorised organisation.
* When a token expires, the integrating system must re-authenticate to obtain a new one.

<Note>
  For credentials, API keys, and onboarding, contact the **medWrite team**.
</Note>

## What's in this reference

| Section            | Description                                                                                  |
| ------------------ | -------------------------------------------------------------------------------------------- |
| **Authentication** | API authentication (API key + bearer token) and embedded authentication for EHR integration. |
| **Get Records**    | Get approved outputs, mark output completed, get attachments, and get PDF documents.         |
| **HL7 Receiver**   | Send HL7 ADT messages and understand HL7 phases (admission, transfer, discharge, etc.).      |

## Next steps

<Columns cols={2}>
  <Card title="API Authentication" icon="key" href="/api-reference/api-authentication">
    API key and bearer token for API access.
  </Card>

  <Card title="Embedded Authentication" icon="shield" href="/api-reference/embedded-authentication">
    Embed MedWrite in your EHR with URL-based auth.
  </Card>
</Columns>