This is mostly an FYI.

It seems like the Geocaching side of oAuth has stopped returning homeCoordinates as a part of the data structure. By looking at your code I assume your tests will fail due to this.

I will try to ask them if it's intentional. The data can still be retrieved with the API method /v{api-version}/users/{referenceCode}. But in my case it means an extra http call upon every oauth. On the other hand I guess most API partners don't use the home coordinates for anything.

Hi.

Project-GC switched from its own oauth implementation to this a few years ago. As you probably know Geocaching.com is making several oAuth changes on the 1st of January 2024. Staging is already updated to that.

Since Project-GC is still using PHP 7.x and it's a major work task to upgrade to 8.x, and might even cause other issues, so you know if your 1.4 oauth version works with the coming changes?

I tried to update my code to authenticate against Staging to verify, but I am this far only getting a http code 500 on their end. Sadly I don't know if I missed changing something in my end or it's because oauth2-geocaching v1.4 is too old. It would have been wise if I tested it before they updated Staging as well.

the geocaching API, Paragraph TOKEN ENDPOINT tells about the response as a JSON construct with the four parts "access_token", "token_type", "expires_in" and "refresh_token".
How can I get the values for this?

Can you provide an example for refreshing the access token by means of the refresh_token ?

The access token seems to expire within a day.