---
title: "getFeedDocument"
method: GET
path: "/feeds/2021-06-30/documents/{feedDocumentId}"
tags: ["Feeds v2021-06-30"]
---

# getFeedDocument

`GET /feeds/2021-06-30/documents/{feedDocumentId}`

Returns the information required for retrieving a feed document's contents.

**Usage Plan:**

| Rate (requests per second) | Burst |
| ---- | ---- |
| 0.0222 | 10 |

The `x-amzn-RateLimit-Limit` response header returns the usage plan rate limits that were applied to the requested operation, when available. The preceding table indicates the default rate and burst values for this operation. Selling partners whose business demands require higher throughput may have higher rate and burst values than those shown here. For more information, refer to [Usage Plans and Rate Limits in the Selling Partner API](https://developer-docs.amazon.com/sp-api/docs/usage-plans-and-rate-limits-in-the-sp-api).

## Path parameters

- `feedDocumentId` string, required

## Query parameters

- `enableContentEncodingUrlHeader` boolean

## Response `200`

Success.

- FeedDocument — Information required for the feed document.
  - `feedDocumentId` string, required — The identifier for the feed document. This identifier is unique only in combination with a seller ID.
  - `url` string, required — A presigned URL for the feed document. If `compressionAlgorithm` is not returned, you can download the feed directly from this URL. This URL expires after 5 minutes.
  - `compressionAlgorithm` 'GZIP' — If the feed document contents have been compressed, the compression algorithm used is returned in this property and you must decompress the feed when you download. Otherwise, you can download the feed directly. Refer to [Step 7. Download the feed processing report](https://developer-docs.amazon/sp-api/docs/feeds-api-v2021-06-30-use-case-guide#step-7-download-the-feed-processing-report) in the use case guide, where sample code is provided.

## Other responses

- `400` — Request has missing or invalid parameters and cannot be parsed.
- `401` — The request's Authorization header is not formatted correctly or does not contain a valid token.
- `403` — Indicates access to the resource is forbidden. Possible reasons include Access Denied, Unauthorized, Expired Token, or Invalid Signature.
- `404` — The specified resource does not exist.
- `415` — The request's Content-Type header is invalid.
- `429` — The frequency of requests was greater than allowed.
- `500` — An unexpected condition occurred that prevented the server from fulfilling the request.
- `503` — Temporary overloading or maintenance of the server.

---

[API](https://skmtc.net/aws-samples/apis/a-content-management-v2020-11-01.md) · [All operations](https://skmtc.net/aws-samples/apis/a-content-management-v2020-11-01/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws-samples/a-content-management-v2020-11-01/revisions/815a5b6dbaa6/schema)