HTTP Request Error 400: /problems/input-validation-error

[reyaldi7]

Hi All,
I'm trying to call an API, but the response got Error 400 with these details:

{

  "type": "/problems/input-validation-error",

  "title": "Input validation error",

  "detail": "Accept-Language: value must be one of the following: bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv",

  "status": 400,

  "instance": "/trademarks/015633043",

  "correlationId": "f8c9fc7aa72888cf"

}

I've successfully request a token and use parse Json to get the access token. 
This is the documentation

This is my Flows

And this the result

Thanks in advance

[Expiscornovus · Accepted solution]

Hi @reyaldi7,

I see in the screenshot of the documentation of the API that an Accept-Language key and value are required in the Headers of your request, that is missing in the HTTP action configuration.

However, that might still not work with the HTTP action though. Because Accept-* type of headers are omitted/removed from the headers by the HTTP action:

https://learn.microsoft.com/en-us/azure/connectors/connectors-native-http#omitted-http-headers

[reyaldi7]

Hi @Expiscornovus 

Yes i get that's the problem
What can I do then to make this happen?
I've got this far really hope it can be done

Also, in the documentation it says that Accept-Language is optional, how can this be required?
I've tried using postman without Accept-Language and it works just fine

[Expiscornovus]

Hi @reyaldi7,

Try and create a custom connector instead. That might be a way to workaround this:

https://learn.microsoft.com/en-us/connectors/custom-connectors/define-blank

And not sure why it is returning Accept-Language as required. I would suggest you speak with somebody whose is supporting that third-party API.

[tfraser · Accepted solution]

Hi @reyaldi7 I've worked around a similar issue (renaming the Authentication header) in the following way, which may or may not help in your scenario: create a custom connector and use that instead of the standard HTTP step. Custom connectors allow you to specify policies applied to a HTTP request which you can use to overwrite some of the headers that are otherwise restricted.

Documentation here: Set HTTP Header | Microsoft Learn

It might seem daunting at first but custom connectors aren't as bad as they look!

I have run in to some issues when importing custom connectors into other environments though.

Example:

[reyaldi7]

@tfraser 
My Goodness sir!
You're a lifesaver! It is working just fine!!!!
Really!! Thank youu!!!