There are quite a few occasions where there are more than four attribute types but we only ever use four. It struck me as sensible to restrict the number of attribute types to four using the va parameter. But take a look at the following API calls:
In this instance there are only four attribute types but I need to be able to apply the parameter across the board. Look what happens when I do that in this instance:
It appears we have an 'off by one' bug for controlling the number of attributes when you've only supplied a keyword (if you include a leaf level category ID in your request, it appears to work fine.) In all honesty, this will most likely not be fixed, as we are focusing on our new API offering, but a couple of ways to work around it might be:
1. Set the number of attributes to 5, and ignore the last one in cases when 5 are actually returned.
2. Set the number of attributes to 5 when you are only querying by keyword, and 4 when you include a category ID.
There are quite a few occasions where there are more than four attribute types but we only ever use four. It struck me as sensible to restrict the number of attribute types to four using the va parameter. But take a look at the following API calls:
http://uknetguide.uk.api.shopping.com/scripts/GSIsapiExt.dll/linkin_id-8005628/Keyword-nail+polish/na-1
In this instance there are only four attribute types but I need to be able to apply the parameter across the board. Look what happens when I do that in this instance:
http://uknetguide.uk.api.shopping.com/scripts/GSIsapiExt.dll/linkin_id-8005628/Keyword-nail+polish/na-14/va-4/
It only returns three attribute types! Can this be right? Am I doing something wrong?
James Taylor – 10/14/08 4:52 am
The first URL should be:
http://uknetguide.uk.api.shopping.com/scripts/GSIsapiExt.dll/linkin_id-8005628/Keyword-nail+polish/na-14
Ryan – 10/14/08 10:07 am
Hi James -
It appears we have an 'off by one' bug for controlling the number of attributes when you've only supplied a keyword (if you include a leaf level category ID in your request, it appears to work fine.) In all honesty, this will most likely not be fixed, as we are focusing on our new API offering, but a couple of ways to work around it might be:
1. Set the number of attributes to 5, and ignore the last one in cases when 5 are actually returned.
2. Set the number of attributes to 5 when you are only querying by keyword, and 4 when you include a category ID.
Hope that helps,
--ryan