We started getting this error on the /profiles API a few days ago even though there has been no change to our app.
{
"errors": [
"status": 400,
"code": "invalid",
"title": "Invalid input.",
"detail": "'subscriptions' must be requested via additional-fields in order to be included as a sparse fieldset",
"source": {
"parameter": "additional-fields"}
]
}
This was not previously required and is not documented at all. Even worse is that it was changed for previous versions of the API, which defeats the purpose of having versions in the first place.
Tagging a “community manager” just to hopefully get some attention on this (@Brian Turcotte ). I don’t have any way of contacting Klaviyo directly.
As far as the first one, we’re always trying to improve and expand the functionality of our APIs, and by doing so we run into an occasional bug - which is why we’re extremely grateful that we have a responsive community of developers like yourself to keep us in the loop on your experience!
Secondly, although I do have a direct line to our Engineers working on the APIs, we do recommend that more urgent, time-sensitive issues be addressed by Support, which is more focused on handling account-critical cases and escalations.
@Brian Turcotte Yes, it looks to be working as before. Thanks
Some questions remain:
The point of API versions is so that things like this don’t happen. Why are changes being made that affect supposedly locked API versions?
Why is there no direct channel of communication with Klaviyo for developers using the Klaviyo API? The change and API errors started on Oct 6. There was an earlier post from another user on this same issue that has gone unanswered. I’m not sure, maybe mine would have gone unanswered as well if I hadn’t specifically tagged you.
As far as the first one, we’re always trying to improve and expand the functionality of our APIs, and by doing so we run into an occasional bug - which is why we’re extremely grateful that we have a responsive community of developers like yourself to keep us in the loop on your experience!
Secondly, although I do have a direct line to our Engineers working on the APIs, we do recommend that more urgent, time-sensitive issues be addressed by Support, which is more focused on handling account-critical cases and escalations.
