expire_in vs expires_in

The Netatmo API is a set of webservices allowing developers and third parties to access Netatmo device's data.
Post Reply
ejain
Posts: 19
Joined: 05 Apr 2013, 08:16

expire_in vs expires_in

Post by ejain » 06 Apr 2013, 03:14

The Netatmo API includes a property named expire_in in responses for access token requests, whereas the OAuth2 standard uses expires_in (see http://tools.ietf.org/html/rfc6749#section-5.1).

Might be worth considering adding expires_in to the response, for people using standard-compliant client libraries? (Or better yet, stop expiring tokens...)

trosenblatt
Posts: 233
Joined: 18 Sep 2012, 12:18

Re: expire_in vs expires_in

Post by trosenblatt » 08 Apr 2013, 11:26

You are right indeed, we have made a mistake, we will change expire_in by expires_in in next backend release (this week).
Sorry for this and thank your for your remark,

Regards.
Thomas Rosenblatt, Netatmo Team.

ejain
Posts: 19
Joined: 05 Apr 2013, 08:16

Re: expire_in vs expires_in

Post by ejain » 08 Apr 2013, 20:12

If possible, could you include both expire_in and expires_in in the response for a while, in order to not break existing applications?

trosenblatt
Posts: 233
Joined: 18 Sep 2012, 12:18

Re: expire_in vs expires_in

Post by trosenblatt » 09 Apr 2013, 14:28

This is what is done now.
Regards,
Thomas Rosenblatt, Netatmo Team.

Post Reply

Return to “Netatmo API”