3. Follow 302 Redirect to Manifest File
Request
Path
GET {MANIFEST_URL}Path tokens
| Name | Description |
|---|---|
{MANIFEST_URL} |
The URL provided in the previous step. |
Response
The response will be a manifest file containing information about what UGC data is available. The following example demonstrates the structure of a manifest file. Your response will have the same format, but may have fewer values depending on your configuration.
{
"question-parent-keys": [
{
"path": "/contents/full/2017-05-04/v2/question-parent-keys/part-1-r-00000.gz",
"recordCount": 469
},
…
],
"comments": [
{
"path": "/contents/full/2017-05-04/v2/comment/part-1-r-00000.gz",
"recordCount": 34
},
…
],
"review-parent-keys": [
{
"path": "/contents/full/2017-05-04/v2/review-parent-keys/part-1-r-00000.gz",
"recordCount": 4543
},
…
],
"reviews": [
{
"path": "/contents/full/2017-05-04/v2/review/part-1-r-00000.gz",
"recordCount": 3255
},
…
],
"configuration": [
{
"path": "/contents/2017-05-04/v2/configuration/config.json",
"recordCount": 1
}
],
"answers": [
{
"path": "/contents/full/2017-05-04/v2/answer/part-1-r-00000.gz",
"recordCount": 680
},
…
],
"questions": [
{
"path": "/contents/full/2017-05-04/v2/question/part-1-r-00000.gz",
"recordCount": 467
},
…
],
"categories": [
{
"path": "/contents/full/2017-05-04/v2/category/part-1-r-00000.gz",
"recordCount": 3
},
…
],
"authors": [
{
"path": "/contents/full/2017-05-04/v2/author/part-1-r-00000.gz",
"recordCount": 4745
},
…
],
"products": [
{
"path": "/contents/full/2017-05-04/v2/product/part-1-r-00000.gz",
"recordCount": 52562
},
…
]
}In the example above, an ellipsis (…) indicates that there may be additional data.
The path values will be used in the next step to request your content.
Updated about 2 months ago
