Skip to content
This repository has been archived by the owner on Sep 26, 2020. It is now read-only.

buildAccountStatsRequest() doesn't work #20

Closed
dimapasko opened this issue Feb 2, 2015 · 5 comments · Fixed by #21
Closed

buildAccountStatsRequest() doesn't work #20

dimapasko opened this issue Feb 2, 2015 · 5 comments · Fixed by #21

Comments

@dimapasko
Copy link

Hi

I'm using fullcontact4j
In following way:

    FullContact fullContact = FullContact.withApiKey(fullContactKey).build();
    AccountStatsRequest accountStatsRequest = fullContact.buildAccountStatsRequest().setPeriod(2015, 1).build();

where fullContactKey is correct API key

For
AccountStatsResponse accountStatsResponse = fullContact.sendRequest(accountStatsRequest);

I'm getting following error:

com.fullcontact.api.libs.fullcontact4j.FullContactException: Invalid period; YYYY-MM format expected
com.fullcontact.api.libs.fullcontact4j.http.FCRetrofitCallback.failure(FCRetrofitCallback.java:69)
at retrofit.CallbackRunnable$2.run(CallbackRunnable.java:53)
at retrofit.Utils$SynchronousExecutor.execute(Utils.java:114)
at retrofit.CallbackRunnable.run(CallbackRunnable.java:51)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at retrofit.Platform$Base$2$1.run(Platform.java:94)

In debbuger i found out that fullcontact4j actually calls https://api.fullcontact.com/v2/stats.json?period=2015-1 without apiKey

It seems that fullContact.buildAccountStatsRequest() doesn't work fine :(

Let me know if i missed something.

Thank you!

@eentzel
Copy link
Contributor

eentzel commented Feb 2, 2015

Thanks @dimapasko! We will get a fixed version released shortly.

@dimapasko
Copy link
Author

@eentzel Great, Thx!

@dimapasko
Copy link
Author

@eentzel @ParisMi
Could you provide version number as soon as it would be available on bitray, please?

ParisMi added a commit that referenced this issue Feb 2, 2015
- changes in this version:
- fixes #20
@ParisMi
Copy link
Contributor

ParisMi commented Feb 2, 2015

should be up there now, 2.1.3.

@dimapasko
Copy link
Author

Thx, it works now 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants