You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move Pinterest API v3 endpoints responsible for fetching Feed workflows and catalog item statuses to v5.
With API v3 when fetching feed workflow there was an AWS S3 file url, which we parsed and displayed the results to the user.
Now instead of a file we have a separate endpoint which returns the list of results for each item_id.
GET v3/catalogs/datasource/feed_report/<MERCHANT ID>/
returns the list of workflows each of which has s3_validation_url property with the link to a file.
When the current v5
GET v5/catalogs/feeds/<FEED ID>/processing_results
returns the list of workflows (now called processing results) which do not include anything similar to s3_validation_url.
And I see there is an endpoint instead
GET v5/catalogs/processing_results/<PROCESSING RESULT ID>/item_issues
which returns a list of items with item_id and errors/warnings per item.
The text was updated successfully, but these errors were encountered:
Move Pinterest API v3 endpoints responsible for fetching Feed workflows and catalog item statuses to v5.
With API v3 when fetching feed workflow there was an AWS S3 file url, which we parsed and displayed the results to the user.
Now instead of a file we have a separate endpoint which returns the list of results for each
item_id
.returns the list of workflows each of which has
s3_validation_url
property with the link to a file.When the current v5
returns the list of workflows (now called processing results) which do not include anything similar to
s3_validation_url
.And I see there is an endpoint instead
which returns a list of items with
item_id
and errors/warnings per item.The text was updated successfully, but these errors were encountered: