# Over rate limit **URL:** \ **Category:** Help\ **Tags:** workflow\ **Created:** [January 14, 2020, 4:41pm UTC](https://forums.losant.com/t/over-rate-limit/2535 "2020-01-14T16:41:50Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [January 14, 2020, 9:47pm UTC](https://forums.losant.com/t/over-rate-limit/2535/5 "2020-01-14T21:47:02Z")
Hi Lars, The [Data Bulk Export by Query](https://docs.losant.com/rest-api/data/#export) action is limited to one call per hour, per the [documentation](https://docs.losant.com/rest-api/overview/#throttles-and-limits). When setting your “end” and “start” values, keep in mind that `start` is the earliest time you would like to start the query, and `end` is the end of the query range, or the latest time you would like to query. Setting `end` to 0 will set the end of the range to `now`. Here are a couple of Forum posts which utilize `start` and `end`: > [@Aggregation LAST yielding unexpected result](https://forums.losant.com/t/aggregation-last-yielding-unexpected-result/2387/5): > > Hi @Alexander_Farley, I apologize for the delay, I had to check with our engineering team for clarification on some behavior. In the coming days, I am going to update the node and schema documentation for Time Series Queries. There are many possible combinations of variables within the Time Series request that produce varying results, and the documentation is lacking around this action. Once I have updated this documentation, I will link it below smile I want to break down a couple of thing… > [@Timeseries query gives fewer results for a strictly-wider time range](https://forums.losant.com/t/timeseries-query-gives-fewer-results-for-a-strictly-wider-time-range/2297): > > I’m using a Losant API node to perform a “Data: Timeseries” query. For the query, I am supplying a start-time and an end-time using a Virtual Button for testing: { "searchstart": 0, "searchend": 1571436455 } Using the above parameters, I get results which suggest that searchstart and searchend are being interpreted as seconds-since-epoch rather than milliseconds-since-epoch as stated here: [https://forums.losant.com/t/schema-for-the-body-of-a-time-series-query/1586/4](https://forums.losant.com/t/schema-for-the-body-of-a-time-series-query/1586/4) The time-series query … > [@REST API Export Problem](https://forums.losant.com/t/rest-api-export-problem/1658/7): > > Hi Julia, I have the answer to the problem. After looking closely at your url, I noticed that the punctuation characters were escaped with a backslash: …/export\?email\=ecn@systemsofmerritt.com\&start\=-1012000\&end\=0 The url below is what was giving us trouble: …/export?email=ecn@systemsofmerritt.com&start=-1012000&end=0 I’m not sure why it even recognized the email, but it only does if it is the first thing after the “?”. I’m also not sure why I was having trouble with the Electric Imp h… Thanks! Julia --- _[View the full topic](https://forums.losant.com/t/over-rate-limit/2535)._