Component for fetching Conversation IDs for given Tweets
Budget: €250 – €750 EUR
Description: the project consists of a component that gets the Tweets from a given account of our internal tool, and extracts the conversation-id and the type of Tweet (normal Tweet, reply or answer) from each tweet.
Preconditions:
- It’s mandatory that you have already implemented some other integrations with the Twitter API.
- Twitter API: the developer needs to create a new Twitter API key and agree to the Twitter terms of service and hand over that key to us after project completion.
- We will create a user account in our internal tool for you.
- We will provide you access to our API documentation for tagging purposes.
The result of the project should be:
- Java code for collecting the information. You can use any open source libraries that you consider necessary.
- A set of unit and integration tests to validate the generated results.
- A .jar file that we can run locally on a MacBook.
- A JSON file that the code generates with each run.
- Some tags added directly via our API.
The result is mandatory by Feb 24th. This deadline is not possible to be changed.
Limits: with a single Twitter API key, one should be able to request something like 900 Tweets per 15 minutes. This component should work for up to 10k tweets/day so using just a single API key might just about be enough for the scale wanted.
Link to conversation_id explanation: https://developer.twitter.com/en/docs/twitter-api/conversation-id
Input: An account of our internal tool.
Outputs:
- a JSON file with the list of conversation-ids. The exact format can be discussed later.
- a tag per conversationId added as a mention directly via our API. The API documentation will be provided later by us.
Preconditions:
- It’s mandatory that you have already implemented some other integrations with the Twitter API.
- Twitter API: the developer needs to create a new Twitter API key and agree to the Twitter terms of service and hand over that key to us after project completion.
- We will create a user account in our internal tool for you.
- We will provide you access to our API documentation for tagging purposes.
The result of the project should be:
- Java code for collecting the information. You can use any open source libraries that you consider necessary.
- A set of unit and integration tests to validate the generated results.
- A .jar file that we can run locally on a MacBook.
- A JSON file that the code generates with each run.
- Some tags added directly via our API.
The result is mandatory by Feb 24th. This deadline is not possible to be changed.
Limits: with a single Twitter API key, one should be able to request something like 900 Tweets per 15 minutes. This component should work for up to 10k tweets/day so using just a single API key might just about be enough for the scale wanted.
Link to conversation_id explanation: https://developer.twitter.com/en/docs/twitter-api/conversation-id
Input: An account of our internal tool.
Outputs:
- a JSON file with the list of conversation-ids. The exact format can be discussed later.
- a tag per conversationId added as a mention directly via our API. The API documentation will be provided later by us.
Related categories:
Business, Accounting, Human Resources & Legal
Twitter
Software Architecture
Twitter API