Announcements
Updates and important changes to the APIs
FineFriends Developers Space
If you want announcements and updates on your feed, you can join the FineFriends Developers Space.
In this space, there will be regular updates and announcements.
Updates to API V3 & V4
February 7 2020
Up until now, it was only possible to register one redirect URL. With this update, it is possible to register multiple URLs. This can be done using the app settings. The previous current redirect URL will remain valid if you do not take action.
What is changing
The changes are in line with the OAuth 2.0 standards. You should pass the redirect_uri paramter when directing users to the authorization page. This parameter must exactly match one of the registered URLs. Also, you should pass the redirect_uri parameter in the POST request to the access_token endpoint.
How to implement
All changes are available in both API V3 and V4. The api_version fields has been changed from 3.0 to 3.1 and from 4.0 to 4.1 with this update. The usage of the new parameters is not required for now. If you do not pass the parameter to the authorization endpoint, the first given return URL will be used by default. If you do not set the parameter at the access_token endpoint, the status will still be "success", but the error field will return the value "invalid_redirect_uri_notice", accompanied by a error_description. In future versions of the API, these fields will be mandatory.
While this update should not break any existing implementations, it is recommended to implements these changes as soon as possible.
Up until now, it was only possible to register one redirect URL. With this update, it is possible to register multiple URLs. This can be done using the app settings. The previous current redirect URL will remain valid if you do not take action.
What is changing
The changes are in line with the OAuth 2.0 standards. You should pass the redirect_uri paramter when directing users to the authorization page. This parameter must exactly match one of the registered URLs. Also, you should pass the redirect_uri parameter in the POST request to the access_token endpoint.
How to implement
All changes are available in both API V3 and V4. The api_version fields has been changed from 3.0 to 3.1 and from 4.0 to 4.1 with this update. The usage of the new parameters is not required for now. If you do not pass the parameter to the authorization endpoint, the first given return URL will be used by default. If you do not set the parameter at the access_token endpoint, the status will still be "success", but the error field will return the value "invalid_redirect_uri_notice", accompanied by a error_description. In future versions of the API, these fields will be mandatory.
While this update should not break any existing implementations, it is recommended to implements these changes as soon as possible.
Deactivation V2
January 27 2020
API Version 2.0 has been deactivated, and will no longer work. Please upgrade to version 4 as soon as possible. If you are using version 3, upgrading to version 4 is recommended. As this version has only some minor changes, upgrading is very simple and by doing so you are prepared for the future deprecation of V3.
API Version 2.0 has been deactivated, and will no longer work. Please upgrade to version 4 as soon as possible. If you are using version 3, upgrading to version 4 is recommended. As this version has only some minor changes, upgrading is very simple and by doing so you are prepared for the future deprecation of V3.
API Version 4 + Deprecation V2
August 1 2019
API version 4.0 has been released. It adds new options to make authentication better adjustable for the needs of your application. The only breaking change is very small and simple to fix. You can find more about version 4, how to upgrade and how to use it on the API documentation page.
With the release of version 4, version 2 has been deprecated. It will stop working soon. Please upgrade your API version to V4 to assure that your application will continue to work.
API version 4.0 has been released. It adds new options to make authentication better adjustable for the needs of your application. The only breaking change is very small and simple to fix. You can find more about version 4, how to upgrade and how to use it on the API documentation page.
With the release of version 4, version 2 has been deprecated. It will stop working soon. Please upgrade your API version to V4 to assure that your application will continue to work.
API Version 3
February 18 2018
The API has been updated to version 3. From this version and up, the API supports the oAuth 2.0 standards. This means that you can now easily use the FineFriends API with existing oAuth applications. Version 3 requires some changes to be made to your code. You can find more about version 3 and how to use it on the API documentation page.
The API has been updated to version 3. From this version and up, the API supports the oAuth 2.0 standards. This means that you can now easily use the FineFriends API with existing oAuth applications. Version 3 requires some changes to be made to your code. You can find more about version 3 and how to use it on the API documentation page.
Changes to API
January 17 2018
The API has changed to solve a security flaw. You will have to update to use the API. Please review the API page for more information on how to update to the new version. We're sorry for the inconvenience.
Apart from this, we made the API faster and easier to implement, requiring less requests and we also improved error handling. We added a section on how to use it to the API page.
The API has changed to solve a security flaw. You will have to update to use the API. Please review the API page for more information on how to update to the new version. We're sorry for the inconvenience.
Apart from this, we made the API faster and easier to implement, requiring less requests and we also improved error handling. We added a section on how to use it to the API page.