Legacy API return error - Server encountered exception: Maximum number of threads throttled

[Pav]

Peter had the same issue a few days ago as mentioned here:

API Restrictions & Rate Limits

Refresh token will not work if you are trying to use it as an access token when making an api call. I would review RFC 6749: The OAuth 2.0 Authorization Framework for getting authorization and making api calls using an access token. You can also look at RFC 6749: The OAuth 2.0 Authorization Framework for using the refresh token to “refresh” your access token. Keap REST API explains how all this works with Infusionsoft. Hopefully that makes sense. Also @John_Borelli has a video I am sure he …

Kyle, tell us if the issue is still occurring. I am also keeping an eye on this as well.

@TomScott - Has anything changed with the Legacy API lately? Two developers have reported the same issue in a few days of each other.