---
title: "Flight Artifact Files"
method: GET
path: "/api/v1/flights/{flight_id}/artifacts"
tags: ["flights"]
---

# Flight Artifact Files

`GET /api/v1/flights/{flight_id}/artifacts`

## Request

- Base URL: `https://api.brumby.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.brumby.com/api/v1/flights/{flight_id}/artifacts`
- Auth: HTTP bearer

What this flight left in S3, with short-lived download links.

S3-only, like the replay session above: the UUID names a fixed directory
(services/flight_artifacts.py), so a flight with no ledger row still answers.
A manual flight has a Cube log and no MCAP, and this is how its page knows.

## Path parameters

- `flight_id` string, uuid, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/brumby/apis/brumby-platform-api.md) - [All operations](https://skmtc.dev/brumby/apis/brumby-platform-api/llms.txt) - [OpenAPI document](https://skmtc.dev/brumby/apis/brumby-platform-api/revisions/fe185e20813e?raw)