Additional Guidelines
|
|
|
|
Encoding Request URLs
All request URIs must be URL-encoded.
Processing Data Elements and Attributes
Make sure that your client application allows new data elements and attributes to be added by AP by ignoring any markup that it does not recognize.
|
|
|
|
When processing data elements and attributes, do not include dependencies on content metadata fields because they are returned only if available and applicable. |
|
|
|
|
ImportantRetrieving Full Item Metadata Using Returned Links
It is recommended that your client application retrieve full metadata using links returned in the search and feed responses instead of constructing those links.
|
|
|
|
This practice is also beneficial since the returned links may contain additional optional parameters used for performance or troubleshooting. |
|
|
|
|
Note
|
|
|
|
To receive pricing information in the Item Metadata responses, make sure to add the |
|
|
|
|
Resetting Ingestion Time
To start ingesting content from a specific point in time, specify the mindate parameter in your feed request; for example:
To get a feed starting with content from two days ago:
Initial feed request (make sure to supply the API key in the x-api-key request header):
https://api.ap.org/media/v/content/feed?q=mindate:>now-2d
To get a feed for a product ID starting with content from a specific date and time:
Initial feed request (make sure to supply the API key in the x-api-key request header):
https://api.ap.org/media/v/content/feed?q=productid:30598+AND+mindate:>2018-09-19T16:22:43Z&page_size=30
All subsequent feed requests must use the next_page link from the previous feed response.
For more examples, see Standard Feed.