This repository was archived by the owner on Sep 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
changelog
ParisMi edited this page Oct 24, 2017
·
29 revisions
- Added support for Company API industries
- Fixed serialization bug of
Organization
s
- Card upload for card reader uses InputStream all the way through to avoid buffering the data in memory
- Fixed a bug where FC4J failed to auto-discover higher limits for the specified keys based on rate limit headers.
- Support specifying Retrofit's
httpExecutor
from the client builder
- Although this is a major version upgrade, this version upgrade should be transparent to all users except those who provide their own OkHttpClient. But even in that case, the upgrade from OkHttp 2 clients to 3 should be a relatively small amount of effort. See https://github.com/square/okhttp/blob/master/CHANGELOG.md
- Added ability to specify rate limiting ExecutorService in client builder
- Fix https://github.com/fullcontact/fullcontact4j/issues/38
- upgrade to OkHttp 2.3.0
- upgrade to Java 7
- Remove some errant references to Java 7 classes, restoring Java 6 compatability
- Support for MacroMeasures in Person API
- Support for the Email Verification API
- The FC4J Rate Limiter now only applies to Person API. Open an issue if this is a problem for you.
- Added a new RateLimitConfig.DISABLED, which does no rate limiting
- Added the ability to get rate limit headers information from FCResponses and FullContactExceptions (getRateLimitsOrNull())
- Added ability to query Person API by SHA256
- Removed Facebook Username and ID lookup, as it is no longer supported through Person API. If this is an issue for you, please contact [email protected].
- Card Reader "View Card" request now properly passes through Access Token
- All request builders now support
customParam
, for supplying custom/bleeding edge parameters - RateLimitPolicy has been replaced with RateLimitConfig, for more generally supplying rate limiting behavior to the client.
- All fields/behavior have been renamed to match
RateLimitConfig
-- changing any references ofRateLimitPolicy
toRateLimitConfig
should preserve behavior and allow compilation. - KeyPerson now has
toPersonRequestOrNull
for easy lookup of a key person's Person API profile
- Key People support for Company API
- CompanyCategory is visibile/accessible
- Support for Company API Requests (https://www.fullcontact.com/developer/docs/company/)
- Fixes #20, where account stats request for January - September would return an error
- Card Reader Upload Request supports webhookId, webhookBody
- Use android-compatible version of Apache Commons (1.2)
- Added support for global request headers using FullContact
customHeaders
builder method
- Dependency on Apache Commons Codec for Base64, removes dependency on Sun code and allows use of library in Android
- CustomParams supported by CardReaderUploadRequest
- Fixed a bug where making a async request with no callback would throw an error
- Fixed a problem where hitting the rate limit for a full minute or more could occasionally result in a rate limit exception.
- SMOOTH rate limiting now allows for 5 seconds of requests, and BURST allows 8.
- FC4J will wait until the next rate limit period if it detects sending a request would return a rate 403 from FullContact
- Fixes Issue #15. Using webhooks with a webhook ID will work now.
- Complete overhaul of library