Hi Chris, pardon the issue here. We have fixed the problem and you can now use the following parameters startDate and endDate to limit the search results.
This seems to correctly return shows in the appropriate range:
http://api.jambase.com/search?startDate=10/28/2009&endDate=10/29/2009&apikey=
But these only return shows with an event date of 10/29/2009:
http://api.jambase.com/search?startDate=10/27/2009&endDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2009&endDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2000&endDate=10/29/2009&apikey=
I'm also seeing inconsistent behavior when using only startDate...
These seem to return shows with an event date of whatever the value of startDate is:
http://api.jambase.com/search?startDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=10/28/2009&apikey=
But these return shows with an event date of 10/29/2009:
http://api.jambase.com/search?startDate=10/27/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2009&apikey=
I'm also a little confused by what is returned when only supplying endDate...it seems to return shows with an event date that is one day after the value of endDate:
http://api.jambase.com/search?endDate=10/29/2009&apikey=
http://api.jambase.com/search?endDate=10/28/2009&apikey=
http://api.jambase.com/search?endDate=10/27/2009&apikey=
http://api.jambase.com/search?endDate=01/01/2009&apikey=
http://api.jambase.com/search?endDate=01/01/2001&apikey=
etc.
Is this the expected behavior when only supplying an endDate?
Thank you for your questions and we apologize for the confusion surrounding these API calls.
startDate & endDate parameters, while fully supported by the API, have been added in as enhancements to our core functionality. As a result there are occasional anomalies with the data returned.
We have, through your comments, discovered and fixed a bug that was causing shows for the day after the endDate to appear in the feed. This has been corrected and you should now see the correct shows when searching by endDate in all situations.
The API does not currently support past show searches, so if you use a date prior to today, that date will automatically be corrected to today's date.
If you only use a startDate without an endDate parameter, then the API will assume you are only trying to retrieve shows for that particular date.
We hope this clarifies and solves your issues. We are eager to make additional enhancements to the API to meet your needs. If you are in need of anything else please let us know and we look forward to working with you.
Thank you for the bug fix and clarifications Andy.
There also seems to be an issue with the 'n' parameter...the following returns a 'too many results' error:
http://api.jambase.com/search?startDate=10/30/2009&endDate=11/06/2009&n=2&apikey=
But these work just fine:
http://api.jambase.com/search?startDate=10/30/2009&endDate=10/31/2009&apikey=
http://api.jambase.com/search?startDate=10/30/2009&endDate=10/31/2009&n=2&apikey=
It seems like the error is being returned before the results list is shortened to the value of 'n'.
Is there a way to set the start and end date in the request parameters?
Jambase Admin – 2 years ago
Yes, include the attributes:
startdate=mm/dd/yyy
enddate=mm/dd/yyyy
to limit the results.
We will update our documentation to reflect this.
Thanks!
Chris – 2 years ago
It doesn't work with my api key. The following example returns all dates...
http://api.jambase.com/search?zip=01701&startdate=10/11/2007&enddate=10/15/2007&apikey=
Jambase Admin – 2 years ago
Hi Chris, pardon the issue here. We have fixed the problem and you can now use the following parameters startDate and endDate to limit the search results.
Thanks for your patience and happy coding!
Dan – 4 weeks ago
I'm also having problems with this...
This seems to correctly return shows in the appropriate range:
http://api.jambase.com/search?startDate=10/28/2009&endDate=10/29/2009&apikey=
But these only return shows with an event date of 10/29/2009:
http://api.jambase.com/search?startDate=10/27/2009&endDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2009&endDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2000&endDate=10/29/2009&apikey=
I'm also seeing inconsistent behavior when using only startDate...
These seem to return shows with an event date of whatever the value of startDate is:
http://api.jambase.com/search?startDate=10/29/2009&apikey=
http://api.jambase.com/search?startDate=10/28/2009&apikey=
But these return shows with an event date of 10/29/2009:
http://api.jambase.com/search?startDate=10/27/2009&apikey=
http://api.jambase.com/search?startDate=01/01/2009&apikey=
I'm also a little confused by what is returned when only supplying endDate...it seems to return shows with an event date that is one day after the value of endDate:
http://api.jambase.com/search?endDate=10/29/2009&apikey=
http://api.jambase.com/search?endDate=10/28/2009&apikey=
http://api.jambase.com/search?endDate=10/27/2009&apikey=
http://api.jambase.com/search?endDate=01/01/2009&apikey=
http://api.jambase.com/search?endDate=01/01/2001&apikey=
etc.
Is this the expected behavior when only supplying an endDate?
Thanks very much.
Jambase Admin – 4 weeks ago
Hi Dan -
Thank you for your questions and we apologize for the confusion surrounding these API calls.
startDate & endDate parameters, while fully supported by the API, have been added in as enhancements to our core functionality. As a result there are occasional anomalies with the data returned.
We have, through your comments, discovered and fixed a bug that was causing shows for the day after the endDate to appear in the feed. This has been corrected and you should now see the correct shows when searching by endDate in all situations.
The API does not currently support past show searches, so if you use a date prior to today, that date will automatically be corrected to today's date.
If you only use a startDate without an endDate parameter, then the API will assume you are only trying to retrieve shows for that particular date.
We hope this clarifies and solves your issues. We are eager to make additional enhancements to the API to meet your needs. If you are in need of anything else please let us know and we look forward to working with you.
Best,
Andy
Dan – 4 weeks ago
Thank you for the bug fix and clarifications Andy.
There also seems to be an issue with the 'n' parameter...the following returns a 'too many results' error:
http://api.jambase.com/search?startDate=10/30/2009&endDate=11/06/2009&n=2&apikey=
But these work just fine:
http://api.jambase.com/search?startDate=10/30/2009&endDate=10/31/2009&apikey=
http://api.jambase.com/search?startDate=10/30/2009&endDate=10/31/2009&n=2&apikey=
It seems like the error is being returned before the results list is shortened to the value of 'n'.
Jambase Admin – 3 weeks ago
Hi Dan -
Pardon this error and our delay in responding. We will look into this and get back to you with a fix shortly.
-Andy