write flask api

[Eik-S]

get_retweeters( post_id: string) #from twitterApi

{ "response": [
    "<userId>",
    "<userId>"] }
  ]
}

get_followers( user_ids: string) #from neo4j

{ "response": {
    "<userId>":
      ["<userId>","<userId>"],
    "<userId>":
      ["<userId>","<userId>"] 
  }
}

get_user_info( user_id: string) #from neo4j or twitterApi

{ "response": {
    "<userId>": {
        "timestamp": 123,
        "name": "<userName>",
        "screen_name": "<screen_name",
        "location": "<location>",
        "lang":"<language>",
        "followers_count": 123,
        "friends_count": 123,
        "statuses_count": 123,
        "created_at":"<timeString>",
        "profile_image_url": "<url>"
    },
    "<userId>": {
        "timestamp": 123,
        "name": "<userName>",
        "screen_name": "<screen_name",
        "location": "<location>",
        "lang":"<language>",
        "followers_count": 123,
        "friends_count": 123,
        "statuses_count": 123,
        "created_at":"<timeString",
        "profile_image_url": "<url>"
    }
  }
}

[Eik-S]

Folder Structure

• crawler
• api
  • twitterRequest
  • serverRequest
  • tokenRequest
  • flaskApi
• tests

[Eik-S]

Some useful resources:

• https://blog.miguelgrinberg.com/post/designing-a-restful-api-with-python-and-flask

API Authentication:

• We can use the example from the tutorial above, using flask_httpauths HTTPBasicAuth
• For better security we should create a simple user database where a hashkey is created for a new user instead of allowing users to create their own password. this hashkey for the front-end is stored in environment variables.

[brunopace]

There is a line in your code like this:

user_dict[ "profile_img_url"] = str(data['profile_image_url'])

Is there a reason why you changed the property name? should we stick to the same convention Twitter uses not to get confused?