---
title: "Retrieve a meeting session artifact"
method: GET
path: "/meeting_sessions/{id}/artifacts/{artifact_id}"
tags: ["Meeting Session Artifacts"]
---

# Retrieve a meeting session artifact

`GET /meeting_sessions/{id}/artifacts/{artifact_id}`

Retrieves a single meeting session artifact by ID.

## Path parameters

- `id` string, required
- `artifact_id` string, required

## Response `200`

Successful response with the meeting session artifact.

- MeetingSessionArtifactResponse
  - `data` MeetingSessionArtifact, required
    - `content` ArtifactContent, required
      - `text` string, required
    - `created_at` string, date-time, required
    - `failure_reason` string, nullable, required
    - `id` string, required
    - `model_provenance` ModelProvenance, required
      - `model` string, required
      - `provider` string, required
    - `session_id` string, required
    - `status` 'pending' | 'completed' | 'failed', required
    - `type` 'summary' | 'action_items', required
    - `updated_at` string, date-time, required

## Other responses

- `401` — Unauthorized. On api.telnyx.com, authentication is enforced by the API gateway before the request reaches the Meeting service, so a missing or invalid API key returns the standard Telnyx error envelope (`{"errors": [{"code": "10009", ...}]}`) rather than the single-`error` shape below.
- `403` — The authenticated credential is not permitted to perform this operation.
- `404` — Not Found
- `429` — Authentication is temporarily overloaded. Retry after the number of seconds in `Retry-After`.
- `500` — Internal Server Error
- `503` — Authentication is temporarily unavailable.

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/3fdc16374d70/schema)