AvatarEditorService.GetRecommendedAssets returns Bad Request if contextAssetId not passed

[lxuca]

AvatarEditorService.GetRecommendedAssets is documented to have contextAssetId as an optional parameter, with it defaulting to 0 and returning generic popular items from the category.
Quote from the documentation: “The contextAssetId is optional and if not provided it will return some popular items from that category.”

However, when I make the request without the parameter I receive HTTP 400 (Bad Request) error. See below for examples.

Without ID (error):

With ID (working as intended):

I’ve tested this with other asset types, and the error is consistent. I’m unsure if this is intended behaviour or not, but I assume it isn’t as the documentation says I should be able to make requests without a contextAssetId.

[thirdtakeonit]

Thanks for the report! I filed a ticket in our internal database.

[BrightYellowElephant]

Hi @lxuca, we are sorry to hear about the issue you are facing. This was a regression on our side and we have identified and fixed the root cause. Please verify and let us know if you are still facing problems. Otherwise we will mark this as fixed.

[lxuca]

Thanks for looking into this! The issue is still persisting for me, perhaps your fix is not live yet?

[BrightYellowElephant]

The fix was rolled out if you call catalog-api directly but it appears the problem still persists if you are calling us via the AvatarEditorService.GetRecommendedAssets, we will take another stab at it and follow up with you again with more updates.

[BrightYellowElephant]

We just deployed a fix today, please try again and let us know if the issue is fixed for you?

[lxuca]

It’s now working as intended, thanks for fixing this!