Description of APIs introduced

• Kayacan Vesek

• Emre Hoşer: I implemented vendortweets endpoint. It takes 1 query parameter that is vendor name. It returns the last 100 tweets of the vendor account. Then, they are pushed in a dictionary and sorted. So, it can be enabled to return the 10 most favorite tweets of the vendor. The API returns the 10 most favorite tweets of a vendor account.

• M. Zeynep Çayırçimen: I implemented searchtrendforproduct endpoint. It takes 1 query parameter that is the product name. It returns the last 100 tweets related to this product. To be able to calculate the popularity, the time difference between 1st and 100th tweets is calculated. Based on the time difference, the average number of tweets posted within 24 hours is estimated and returned to the user. Our API determines a product's popularity in this way.

• Volkan Bulca: I implemented searchtrendforvendor endpoint. It takes 1 query parameter as vendor name and searches all the tweets that contain that vendor name as mentioned in it. Then, it finds the last 100 tweets (maximum amount of tweets can be found by our twitter token), if possible, and looks for the duration that people search for that vendor. At last, it calculates the estimation for average searchs for vendors within 24 hours. That API basically indicates the popularity of a vendor by the users.

• Mısra Yavuz: I implemented filter_user_tweets endpoint. It takes 3 query parameters: user, mentioned and count. count is for the number of tweets wanted, user is the Twitter username of whom tweets will be searched and mentioned is the Twitter username of the vendor. The functionality of this API, that is why it is useful for our platform, is to get evaluations and complaints of the vendors we have on our platform by specific people(mainly critics, magazines and etc.). Response should be a JSON string of an array consisting of mentioned tweets of the vendor by user, ordered from most recent to least. If there is none, it is an empty list.

• Sertay Akpınar: I implemented showfollowers endpoint. It takes 1 query parameter which is the screen name. The screen name is the Twitter user name. The user can be a customer, vendor, or even an e-commerce platform. Popularity is one of the ways to impress people and undoubtedly, the number of twitter followers is one of the things that determines popularity. My goal was to show the popularity of each user by returning the number of twitter followers. Basically, my API accessed the user’s data and returns the follower count value of the data.

• Yaşar Selçuk Çalışkan: I implemented exchangerates endpoint. It makes an HTTP request to the exchange rates API I used and sends the results to the front-end. I used a promise-based HTTP client for node.js called Axios. Using Axios, real-time exchange rates for 33 currencies based on the Turkish lira are obtained.

• İsmet Sarı: I implemented twittercomments endpoint. It requires from user only what parameter which is the name of the product and searches all 100 tweets and takes all of them with text and other properties of the tweets. After all, sort the tweets by the number of favorite count and return the top 10 popular tweets.

• Muhammed Halas: I implemented the database/addproduct endpoint. It takes parameters "name", "price", "color", "rating", "size", "comments" as form-data/key-value-pairs and then inserts a new product to the database and returns the information of the new product.

• M. Emre Demir: I implemented the database/thelist endpoint which returns the top-rated 20 products in the database. This endpoint does not take parameters and fully public. The reason behind this is to share public data and reward the vendors with good products.