Closed

7x Search/Social Media Client API implementations

Client API implementations across search/social media APIs calling Google, Facebook, Linkedin, Twitter, Majestic, and Buzzumo.

Implementation in Java (8, 9 or 10); expected deliverable is a maven project for each API with a class for the client API, and an accompany integration test.

Google API: cpc, and 8 other fields for a specified client domain name and list of keywords.

Google API: rank information per keyword for a specified competitor domain name and list of keywords

Twitter API: repeating group of tweet information (per tweet) for specified client authorisation information (i.e. for a single client)

Facebook API: repeating group of post information (per post) for specified client authorisation information (i.e. for a single client)

Linkedin API: repeating group of article information (per article) for specified client authorisation information (i.e. for a single client)

Buzzumo API: share information across FB, Twitter, Reddit etc for a specified Buzzumo account and domain.

Majestic API: repeating group containing backlink and flow information per url for a specified API key and list of URLs.

- Classes, methods, field names, and variables should be of a sensible length.
- Each client implementation should contain as few classes as possible to achieve clean design; each class should have a single purpose and follow GRASP principles. Each API web-service implementation should define the following classes:
o A pojo class encapsulating the response fields, with accessor methods for each field.
o A class wrapping the API web-service taking in any necessary parameters in an instance method (i.e. not a constructor), and the method should return a response POJO containing the fields defined as required by 10point6.com.
o An integration test client for the API wrapper.
- Project Lombok annotations should be used in POJOs to achieve minimal boiler-plate code.
- Apache commons-lang/Google Guava libraries can be used necessary.
- Code comments should be written using standard Javadoc; Each class should define a class-level Javadoc comment and all public methods should be similarly documented, including parameters. @see annotations should be used to point to relevant API documentation where necessary.
- Delivered code should compile without error using maven clean install.
- Code should be free of Eclipse/IntelliJ warnings.

- Classes, methods, field names, and variables should be of a sensible length.
- Each client implementation should contain as few classes as possible to achieve clean design; each class should have a single purpose and follow GRASP principles. Each API web-service implementation should define the following classes:
o A pojo class encapsulating the response fields, with accessor methods for each field.
o A class wrapping the API web-service taking in any necessary parameters in an instance method (i.e. not a constructor), and the method should return a response POJO containing the fields defined as required by 10point6.com.
o An integration test client for the API wrapper.
- Project Lombok annotations should be used in POJOs to achieve minimal boiler-plate code.
- Apache commons-lang/Google Guava libraries can be used necessary.
- Code comments should be written using standard Javadoc; Each class should define a class-level Javadoc comment and all public methods should be similarly documented, including parameters. @see annotations should be used to point to relevant API documentation where necessary.
- Delivered code should compile without error using maven clean install.
- Code should be free of Eclipse/IntelliJ warnings.

- Classes, methods, field names, and variables should be of a sensible length.
- Each client implementation should contain as few classes as possible to achieve clean design; each class should have a single purpose and follow GRASP principles. Each API web-service implementation should define the following classes:
o A pojo class encapsulating the response fields, with accessor methods for each field.
o A class wrapping the API web-service taking in any necessary parameters in an instance method (i.e. not a constructor), and the method should return a response POJO containing the fields defined as required by 10point6.com.
o An integration test client for the API wrapper.
- Project Lombok annotations should be used in POJOs to achieve minimal boiler-plate code.
- Apache commons-lang/Google Guava libraries can be used necessary.
- Code comments should be written using standard Javadoc; Each class should define a class-level Javadoc comment and all public methods should be similarly documented, including parameters. @see annotations should be used to point to relevant API documentation where necessary.
- Delivered code should compile without error using maven clean install.
- Code should be free of Eclipse/IntelliJ warnings.

Note: the developer must be able to identify the relevant search/social media APIs to retrieve the specified data.

Taidot: API, Java

Näytä lisää: social media data entry, implementation of binary search tree in data structure, social media data collection, search social media by email, social media data providers, social media data provider, excel social media data, social media data excel, social media data analyst, social media api, twitter social media search engine, social media implementation plan template, python api social media, social media search engine, social media search

Tietoa työnantajasta:
( 0 arvostelua ) United Kingdom

Projektin tunnus: #17349311