I’ve been writing an application which uses the /feed endpoint in the API. I’ve run into problems while testing due to an error being returned every time.
The error returned states that the “type” field is missing but it is there and valid. Currently, there is only one valid value for “type” which is “basic”. Even when present in a request, an error is returned. This behaves the same from my program and from the developers.monzo.com interface online.
I haven’t used the Monzo API, so only taking a quick guess by looking at the docs.
Do you have any requests working to another endpoint? Having a quick look over the docs it looks like the API takes simple name value pairs as post data, but it looks like you’re sending JSON.
The API may full well accept JSON (or the app you’re using convert to name value pairs), though.
I have plenty of requests to other endpoints, which work without issue and as expected.
In the image I posted, it shows the Monzo developers UI which uses JSON and transforms it into form data - I believe this is to make it easier to play around with.
My request to the /feed endpoint, uses valid form data/name-key pairs with the correct content type - it’s pretty much a direct implementation of the Docs.
Do you have a trace ID for the API call? It should be part of the returned HTTP headers. If you can find it, I can take a peak tomorrow and see what’s gone wrong.
Yep this looks like a bug. But it shouldn’t prevent the feed item from being created, only prevent a push notification from being sent.
The bad_request.missing_param.type is percolating up from deep in our stack the missing type hasn’t got anything to do with the type specified in the API.
!