API Response Time By Region

[sprout_will]

We've noticed a large difference between API response times across various regions - we've averaged the response times over the course of 24 hours and compared across several regions:
North America: ~150ms - 200ms

Australia: ~300ms - 400ms

Singapore: ~350ms - 425ms

While this may not seem like a major issue, we make consecutive Fitbit API calls, so the response time difference can add up when comparing regions.

Though this behaviour is somewhat expected, we're curious if there is a potential solution to this problem on Fitbit's end or if a recommended solution could be provided that we could implement on ours (outside of simply making less consecutive calls/splitting the workload, this would most likely be a last resort, but is still an option).

Thanks

[JohnFitbit]

Hi @sprout_will

We'd like to confirm your finding, and if necessary, follow up with engineering.

Could you please DM me the following information?

• Your Client ID
• Which endpoints you're calling?
• Are you using the Subscriptions API?

Thanks! Hope to hear from you soon.