Jump to content


List method At parameter needs further clarification

streams list at

  • Please log in to reply
No replies to this topic

#1 Zambiot


    Advanced Member

  • Members
  • PipPipPip
  • 94 posts
  • LocationAsia

Posted 01 April 2013 - 02:24 PM

I've been playing with the List method of Streams.  The "At" parameter and "Created_at" parameter could use some further explanation.  What tripped me up is the the FROM and TO modifier I had backwards.  I had it expressed in my code similar to what it is in the API docs in the order of TO and FROM.  I was getting 200 OK responses but there was no data returned.  No error either.  However, it looks like it should be that FROM is the lower time value (furtherest in the past) and TO is the highest time value and nearest to the present.


I'd like to recommend that text be added in the API document to help clarify the parameters and to provide examples.  Also, perhaps a check could be built into the API parser to give an error or perhaps switch the values around to make sense and then return data.  


An example of good ordering of data:





The above is an example of a proper ordering of values.  The At_from should be the smaller time value and At_to should be the higher time value.  

Also tagged with one or more of these keywords: streams, list, at

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users