Hello, I would like to know if it is possible to get time data but like every 15 second of the activity instead of each second ?
Thanks in advance,
Pierre
Hello, I would like to know if it is possible to get time data but like every 15 second of the activity instead of each second ?
Thanks in advance,
Pierre
There’s no way to change the data returned from the streams. If you want something less frequent you will need to do processing on your side to get the data you want. Either taking every 15th data point in isolation or calculating averages for the stream in blocks of 15s.
There’s no way to change the data returned from the streams. If you want something less frequent you will need to do processing on your side to get the data you want. Either taking every 15th data point in isolation or calculating averages for the stream in blocks of 15s.
Thank you ! do you have any tips then to not be limited by the max number of request per 15mn ?
There’s no way to change the data returned from the streams. If you want something less frequent you will need to do processing on your side to get the data you want. Either taking every 15th data point in isolation or calculating averages for the stream in blocks of 15s.
Thank you ! do you have any tips then to not be limited by the max number of request per 15mn ?
If you’re hitting your rate limits, you’ll either need to request an increase or space out your requests.
All requests return your current API usage in the headers so you can use that to determine whether you have enough requests left in a 15m block. If your backend processing is set up to use a queue of requests, you can keep serving them until you hit the rate limit, then wait for the next 15m interval to tick over before resuming processing. Using that approach will let you smooth out usage over time, at the cost of things being a little delayed occasionally if there is a sudden burst of requests.
Also make sure you’re using the API as efficiently as possible. Meaning for streams, request all the streams you need in a single request rather than one at a time. Or for other API calls, if they have pagination be sure to request the maximum number of results you’ll need (most have a max of 200/page).
There’s no way to change the data returned from the streams. If you want something less frequent you will need to do processing on your side to get the data you want. Either taking every 15th data point in isolation or calculating averages for the stream in blocks of 15s.
Thank you ! do you have any tips then to not be limited by the max number of request per 15mn ?
If you’re hitting your rate limits, you’ll either need to request an increase or space out your requests.
All requests return your current API usage in the headers so you can use that to determine whether you have enough requests left in a 15m block. If your backend processing is set up to use a queue of requests, you can keep serving them until you hit the rate limit, then wait for the next 15m interval to tick over before resuming processing. Using that approach will let you smooth out usage over time, at the cost of things being a little delayed occasionally if there is a sudden burst of requests.
Also make sure you’re using the API as efficiently as possible. Meaning for streams, request all the streams you need in a single request rather than one at a time. Or for other API calls, if they have pagination be sure to request the maximum number of results you’ll need (most have a max of 200/page).
Super, thank you !
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.