type parameter in /release/search ignored

8 views
Skip to first unread message

Martin Bruse

unread,
Nov 16, 2011, 8:09:33 AM11/16/11
to 7digital API Developers
When I try to find singles by Madonna, for example, I do:

http://api.7digital.com/1.2/release/search?oauth_consumer_key=KEY&q=madonna&type=single

But the first match returned is of type Album. What am I doing wrong?

Also, I have noticed some discrepancies in your documentation. For
example, you are able to sort /release/search using the sort parameter
(even if it is only mentioned in /artist/search). Nice with more
features, but it's cumbersome to know that there may be undocumented
features that you want to use, and just trial and error your way
through them :/

regards,
//Martin

Hibri Marzook

unread,
Nov 16, 2011, 8:29:34 AM11/16/11
to 7digit...@googlegroups.com
Hi Martin,

The type parameter is not implemented properly yet, there are a few
bugs. You aren't doing anything wrong.

You should stick to what is documented only, and if the behaviour
differs please let us know. We will always document what we support
and should be used.

Martin Bruse

unread,
Nov 17, 2011, 5:53:35 AM11/17/11
to 7digital API Developers
So, does this mean I should stop using the sort parameter in /release/
search? Or is it something that you will get around to documenting any
day now? :)

On Nov 16, 2:29 pm, Hibri Marzook <hibri.marz...@gmail.com> wrote:
> Hi Martin,
>
> The type parameter is not implemented properly yet, there are a few
> bugs. You aren't doing anything wrong.
>
> You should stick to what is documented only, and if the behaviour
> differs please let us know. We will always document what we support
> and should be used.
>
> On 16 November 2011 13:09, Martin Bruse <zondol...@gmail.com> wrote:
>
>
>
>
>
>
>
> > When I try to find singles by Madonna, for example, I do:
>
> >http://api.7digital.com/1.2/release/search?oauth_consumer_key=KEY&q=m...

filip

unread,
Nov 22, 2011, 6:32:31 AM11/22/11
to 7digital API Developers
Hi Martin,

any undocumented functionality will be either experimental or work in
progress.

The functionality might still have bugs, change without advance
warning and in some cases might even be dropped altogether. So we
would strongly recommend not to rely on it in production services.

We will update the documentation and let everyone know once it's fully
ready and officially supported.

Thanks
Filip
7digital

Reply all
Reply to author
Forward
0 new messages