This endpoint provides a Feed that can contain Recipes by default and other types of items on demand.
Pagination
We use cursor-based pagination, you can read more about it here: cursor pagination.
Each request without specifying cursors will create a new feed thread with a unique id which you can find in response. While you use cursors you will traverse by one thread and there will not be any duplicates. We do not ensure that you will get the same items in different feed threads.
You can get the same feed using a feed identifier in query parameters (id=...).
It can be useful when you want to iterate by the same feed (e.g. When a user updates page or opens app shortly after the first visit.).
The feed is created for 12 hours after that, you will get a new feed, even if you use the same feed identifier.
Personalization
If user tokenis used, user properties will be considered in resulting feed e.g diets and avoidances.
Also, we consider region in feed items calculations. Country code will be retrieved from user settings if a user token is used. Or you can force country in feed request parameters.
Feed content
We provide different types of feed content. By default, it is the only recipebut you can specify other types in parameter allowedTypes.
Step 2: If the user clicks on one of the group items in the feed, you can get specific feed for items related to this group. All you need is pass field filterKeyfrom group FeedElement into filterKeyparameter of a feed request.
Tip: Feed API can be used to implement rotation for featured recipes. You can specify the size of the feed and rotate items using provided cursors in the required timing.