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

# Quickstart

> Fetch your Replay memories with an API key.

This guide takes you from an API key to your first memory response.

## Prerequisites

Before you begin, you need:

* A Replay account
* At least one memory in your account
* An API key from your account settings in the Replay web app
* The public API base URL for your environment

<Steps>
  <Step title="Get your API key">
    Open the Replay web app and go to your account settings. Create or copy an API key.

    Keep this key private. It can read memories from your account.
  </Step>

  <Step title="Set local environment variables">
    Store the API base URL and API key in environment variables.

    ```bash theme={null}
    export REPLAY_PUBLIC_API_URL="https://api.runreplay.com"
    export REPLAY_API_KEY="rpa_..."
    ```

    If your account settings show a different API endpoint, use that endpoint.
  </Step>

  <Step title="List your memories">
    Call `GET /v1/memories`.

    ```bash theme={null}
    curl --request GET \
      --url "$REPLAY_PUBLIC_API_URL/v1/memories" \
      --header "Authorization: Bearer $REPLAY_API_KEY"
    ```

    The response is an array of memories owned by your account.
    Media URL fields are temporary signed URLs that expire 1 hour after the response is created.
  </Step>

  <Step title="Fetch one memory">
    Copy a memory `id` from the list response and call `GET /v1/memories/{memory_id}`.

    ```bash theme={null}
    curl --request GET \
      --url "$REPLAY_PUBLIC_API_URL/v1/memories/mem_01JZ8W2X4M9QK7F3T6V1N0P8RA" \
      --header "Authorization: Bearer $REPLAY_API_KEY"
    ```
  </Step>
</Steps>

## Example response

```json theme={null}
{
  "id": "mem_01JZ8W2X4M9QK7F3T6V1N0P8RA",
  "name": "Product planning walk",
  "started_at": "2026-06-01T16:02:11Z",
  "ended_at": "2026-06-01T16:18:42Z",
  "is_processing": false,
  "user_id": "user_8ad5a3d1-7f24-4fc4-bf76-07fef4f8a92d",
  "duration_seconds": 991,
  "audio_url": "https://gpngkwsgfwohtyenjaks.supabase.co/storage/v1/object/sign/memories/mem_01JZ8W2X4M9QK7F3T6V1N0P8RA/audio.m4a?token=eyJ...",
  "video_url": "https://gpngkwsgfwohtyenjaks.supabase.co/storage/v1/object/sign/memories/mem_01JZ8W2X4M9QK7F3T6V1N0P8RA/video.mp4?token=eyJ...",
  "preview_image_url": "https://gpngkwsgfwohtyenjaks.supabase.co/storage/v1/object/sign/memories/mem_01JZ8W2X4M9QK7F3T6V1N0P8RA/preview.jpg?token=eyJ...",
  "transcript": {
    "segments": [
      {
        "speaker": "Speaker 1",
        "start_at": "2026-06-01T16:02:23.400Z",
        "end_at": "2026-06-01T16:02:29.900Z",
        "text": "We talked through the public API launch."
      }
    ]
  },
  "summary": {
    "quick_summary": "A planning conversation about the public API launch.",
    "key_takeaways": [
      "Ship read-only access first.",
      "Expose memory list and detail endpoints."
    ]
  }
}
```

## Next steps

* Review [authentication](/authentication)
* Read the [memory model](/concepts/memories)
* Open the [API reference](/api-reference/get-memory)