---
title: "Fetch a File by Engagement and File UUIDs"
method: GET
path: "/v1/engagements/{engagement_uuid}/files/{file_uuid}"
tags: ["engagements", "files"]
---

# Fetch a File by Engagement and File UUIDs

`GET /v1/engagements/{engagement_uuid}/files/{file_uuid}`

## Path parameters

- `engagement_uuid` string, uuid, required
- `file_uuid` string, uuid, required

## Response `200`

The Engagement File with the specified UUID

- object
  - `data` EngagementFileRead, required
    - `name` string, required
    - `size` number, required
    - `mime_type` string, required
    - `url` string, uri, nullable, required
    - `url_expiration` string, date-time, nullable, required
    - `uuid` string, uuid, required
    - `created_at` string, date-time, required
    - `updated_at` string, date-time, nullable, required
    - `engagement_uuid` string, uuid, required — The UUID of the Engagement this File is associated with
    - `folder_uuid` string, uuid, nullable, required — The UUID of the Folder this File is associated with, or null if it sits at the Engagement root.
    - `_links` EngagementFileReadLinks, required
      - `fieldguide` HalLink, required
        - `href` string, uri, required
        - `title` string — A human-readable title for the link
        - `type` string, required — The content-type

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden (requires scopes `engagements.files:read`)
- `404` — Resource not found
- `429` — Too many requests

---

[API](https://skmtc.net/fieldguide/apis/fieldguide-api.md) · [All operations](https://skmtc.net/fieldguide/apis/fieldguide-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fieldguide/fieldguide-api/revisions/6f6009a58cdd/schema)