harvest-client is a Java client for the Harvest REST API (https://help.getharvest.com/api-v2/)
With harvest-client you can use the Harvest v2 API with a nice Java interface:
// Load configuration from application.conf in src/main/resources of your application
Harvest harvest = new Harvest();
// list all users
List<User> users = harvest.users().list();
for (User user : users) {
log.debug("Found user: {}", user);
}
// create new user
User userInfo = ImmutableUser.builder()
.firstName("first")
.lastName("last")
.email("test@example.com")
.build();
User newUser = harvest.users().create(userInfo);
Have a look in the test folders for examples. Each API endpoint has a Create, List and Update test class.
We use github package registry to publish this project
implementation 'ch.aaap:harvest-client:$version'
<dependency>
<groupId>ch.aaap</groupId>
<artifactId>harvest-client</artifactId>
<version>$version</version>
</dependency>
Packages for this project are first pushed to Github Package Registry (and then to maven central, not implemented yet). To use it as a dependency from there:
- add the following to your build.gradle file:
repositories {
maven {
name = "GitHubPackages"
url = uri("https://maven.pkg.github.com/3ap-ag/harvest-client")
credentials {
username = project.findProperty("gpr.user") ?: System.getenv("GH_USERNAME")
password = project.findProperty("gpr.key") ?: System.getenv("GH_TOKEN")
}
content {
// this repository *only* contains artifacts with this group
includeGroup "ch.aaap"
}
}
}
Using Github package repositories need authentication: see Installing a Package from Github Registry
2. You need to create a personal github token with the permissions: read:packages
-
Then have it defined either as env. variables in
GH_USERNAME
andGH_TOKEN
or you can add it as gradle properties, e.g. in ~/.gradle/gradle.properties usinggpr.user
andgpr.key
. -
Add the dependency, e.g. add to build.gradle:
dependencies {
implementation 'ch.aaap:harvest-client:1.1.4'
}
- Set new project.version in build.gradle
- Use a github token with at least these permissions:
write:packages
. See About Tokens - Run
gradle publish
- Java 8 (or higher)
- Gradle
- Clone or fork this repository
- Get a personal access token from Harvest
- Attention: unit tests assume admin access. Don't run them against a production account!
- Configuring your Harvest account id and authentication token:
- You will need 2 Harvest accounts with admin access (it's a limitation of the current Harvest API)
- Either copy reference.conf to src/test/resources/admin{1,2}.conf and insert your credentials
- Or set the following environment properties:
$ export HARVEST_ACCOUNT_ID_ADMIN1=YOUR_ACCT_ID_1 $ export HARVEST_AUTH_TOKEN_ADMIN1=YOUR_AUTH_TOKEN_1 $ export HARVEST_ACCOUNT_ID_ADMIN2=YOUR_ACCT_ID_2 $ export HARVEST_AUTH_TOKEN_ADMIN2=YOUR_AUTH_TOKEN_2
- Run
gradle build
in the root directory of the repository
Go to Harvest Sign up
- Use your 3ap email with a "+" added to the name, e.g. marco+Jul2020@3ap.ch (this way you can create a filter in gmail to archive the emails you get)
- Choose "Me and my team"
- Select "Next Step" until the end.
- Go to "Settings" -> "Chose Modules" -> Tick all modules
- ! Only for the second account: Go to "Settings" -> "Edit Preferences" -> Set Time Mode to "Track time via start and end time"
- Top left on your name -> My Profile -> link under work email to your Harvest ID settings -> Developers -> create new personal Token (name does not matter) Account ID and token are needed for authentication
- Add your token to the local files admin1.conf and admin2.conf under src/test/resources/admin*.conf
- Update the github secrets with these Id and tokens (you might need help from someone who has access to it on github)
You can see the actual HTTP request and response by setting the log level for ch.aaap.harvestclient.core.Harvest.http to TRACE
<Logger name="ch.aaap.harvestclient.core.Harvest.http" level="trace" additivity="false">
<AppenderRef ref="Console"/>
</Logger>
Check out TestSetupUtil.prepareForHarvestBugReport() to setup your logs before sending them to Harvest.
We welcome contributions in the form of pull requests or bug reports! Please read Developers before submitting a pull request. If you plan a big change, please open an issue first so you can get early feedback on your design.