5. Follow 302 Redirect to UGC Data File

Finally, your application should follow the HTTP 302 redirect from the previous step to get the UGC data file.




Path tokens

Name Description

The URL provided in the previous step.


The response will be a gzipped file containing the user generated content (UGC). The contents of each file will vary with the type of UGC. Refer to the Reference section for details on each data set. The following are incomplete examples provided to give a representative sample of what to expect:

{"type":"product", "id":"SomeProductID21", "productField1": "Some Content", … }  
{"type":"product", "id":"SomeProductID83", "productField1": "Some Content", … }  
{"type":"review", "id":"SomeReviewID1", "productId":["SomeProductID83"], "reviewField1":"Some Content", … }  
{"type":"review", "id":"SomeReviewID2", "productId":["SomeProductID21","SomeProductID134"], "reviewField1":"Some Content", … }  

In the examples above, an ellipsis (…) indicates that there may be additional data.

UGC data files may have multiple JSON objects, each on its own line, as demonstrated above. However, the file itself is not valid JSON; Attempting to translate a whole file as JSON will fail. Instead, your application should read the files line-by-line, processing each object individually.