Migrating oauth1 users to auth2 fails after getting 16 new tokens

[TheOldMan]

I have 419 oauth1 secret/tokens to convert to oauth2 access/refresh tokens. I have a little script that fetches the oauth1 values from a db, does the refresh_token call, and writes the new values to the database. This all works great for the first 16 pairs. The 17th one returns 401. I know that the secret/token pair is correct because I can access fitbit using them with oauth1. Is there a limit to the number of times/minute that I can call the converter? Do I need to pause a minute or so after every 15?

Also the oauth2 document says that the conversion should be called only once per oauth1 token pair. What problem will occur if I call it several times for the same pair while I figure out this problem?

[JeremiahFitbit · Accepted solution]

That shouldn't be happening. If you continue to see this, please contact us privately with your client id.

---

@TheOldMan wrote:

Also the oauth2 document says that the conversion should be called only once per oauth1 token pair. What problem will occur if I call it several times for the same pair while I figure out this problem?

---

You're fine to call this multiple times per user. We meant to say that you should ideally only do this process once. We don't want apps relying on this functionality for anything but upgrading to OAuth 2.0, as it will be removed with OAuth 1.0a.

[TheOldMan]

I changed our procedure to make the upgrade when the user attempts to access his Fitbit data. That way we only make a few calls per day. What is the drop-dead date for removal of this utility?

[JeremiahFitbit]

---

@TheOldMan wrote:

What is the drop-dead date for removal of this utility?

---

The OAuth 1.0a to OAuth 2.0 token upgrade feature will be removed when OAuth 1.0a is removed: April 12, 2016.