> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/rest-api-reference/create-source/get-source.md).

# Get Source

Retrieve extracted text and source status by ID, including failure messages and client-side transcript cleaning.

Retrieve extracted content by source ID.

## Endpoint

```
GET https://backend.blotato.com/v2/source-resolutions-v3/:id
```

## Authentication

Include your Blotato API key in the request headers:

```
blotato-api-key: YOUR_API_KEY
```

## Parameters

| Parameter | Type   | Required | Description                                        |
| --------- | ------ | -------- | -------------------------------------------------- |
| `id`      | string | Yes      | The source resolution ID (UUID) from Create Source |

## Clean Transcript Option

`cleanTranscript` is not a REST query parameter or an MCP tool argument. The n8n Blotato node's Source > Get operation provides a local Clean Transcript option, enabled by default. It processes the returned content after the API request.

For REST or MCP, retrieve the completed `content` first, then remove transcript timestamps in your agent or workflow if requested. Do not send `cleanTranscript` to this endpoint expecting it to change the response.

## Response

### Processing (poll again)

```json
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "processing"
}
```

### Completed

```json
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "completed",
  "title": "Video Title",
  "content": "Extracted text content...",
  "referenceUrl": "https://original-source-url.com"
}
```

### Failed

```json
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "status": "failed",
  "message": "Error description"
}
```

## Status Values

| Status       | Description                              |
| ------------ | ---------------------------------------- |
| `queued`     | Source submitted, waiting to process     |
| `processing` | Extraction in progress                   |
| `completed`  | Extraction successful, content available |
| `failed`     | Extraction failed, check message field   |

## Polling Pattern

Source extraction is asynchronous. After calling Create Source:

1. Wait at least 10 seconds
2. Call Get Source with the ID
3. If status is `queued` or `processing`, wait and retry
4. If status is `completed`, use the `content` field
5. If status is `failed`, check the `message` field

## n8n and Make.com

In the official Blotato nodes:

1. Add a Blotato node
2. Select "Source" > "Get"
3. Pass in the source ID from "Create Source"
4. Add a Wait node of at least 10 seconds between status checks
5. The extracted content appears in the response


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/rest-api-reference/create-source/get-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.