> As far as I see it, the function for getting upcoming concerts takes as parameter the internal songkick artist ID, which I would need to get via another function first - or not?
Yes that's true. This is because artist names are not unique, and it would be ambiguous to use that to identify an artist. If you have a limited set of artists you want to search on, you could cache those ids locally.
--
Sabrina Leandro
On Tuesday, 1 May 2012 at 14:21, Thomas Henz wrote:
> Hi Sabrina,
>
> use case would be "get all upcoming concerts in Germany for <artist>" where <artist> would be the actual name, eg U2, The Gaslight Anthem etc.
>
> As far as I see it, the function for getting upcoming concerts takes as parameter the internal songkick artist ID, which I would need to get via another function first - or not?
>
> Thanks a lot,
> Thomas
>
> > > just test-implementing the Songkick API for our web site (www.valve- (
http://www.valve-) (
http://www.valve-)
> > >
magazine.net (
http://magazine.net) (
http://magazine.net)) and wondering, if it is really required to do 2 API
> > > calls to get all events for an artist like
> > > 1.) get artist ID
> > > 2.) get events for artist ID
> > >
> > > Is there a way around that?
> > >
> > > Thanks a lot!
> > > Thomas
> >
>
>
> --
> You received this message because you are subscribed to the Google Groups "Songkick API" group.
> To post to this group, send email to
songki...@googlegroups.com (mailto:
songki...@googlegroups.com).
> To unsubscribe from this group, send email to
songkick-api...@googlegroups.com (mailto:
songkick-api...@googlegroups.com).
> For more options, visit this group at
http://groups.google.com/group/songkick-api?hl=en.