Http request : is there hidden HEADERS parameters?

Questions
1

Hi all,
i try to read a product with a PIM API Get products (akeneo).
I got good response from appsmith and postman but not from N8N.
It always give an error response :

ERROR: UNKNOWN ERROR - check the detailed error for more information
"application/json,text/*;q=0.99" in "Accept" header is not valid. Only "application/json" is allowed.

This seem to be autogenerated.
I only have Authorization header.
I already see this in your execution_entity Table in data field.

I try to write an accept : application/json header, but it does not work.

Thanks for help.

2

Find it !

you can surcharge the Accept value if you write it in MINUS…

accept and not Accept

:shushing_face:

3

Hi, can you send me a picture of how you send the client id and secret, i can’t connect to my Akeneo.

4

hi @victormiranda the akeneo complete guide : The "Connect the PIM" tutorial | Akeneo APIs

You have to get a token that you can use in your request
how to generate a token

image
image1338Ă—934 134 KB

Base64 encoded : Genesys Cloud Developer Center

you get this

image
image1175Ă—261 53.6 KB

call pim api
Bearer {{$node[“Pim Get Token”].json[“access_token”]}}

image
image448Ă—984 37.6 KB

5

Thanks you, but inside Authorization’s value (in header) you write the client id and secret.
In what format are they written, all together without spaces?

6

You have to encode it

Base64 encoded : Genesys Cloud Developer Center

7

Thanks a lot.

8

Hi other time,
i have other problem with akeneo, i don’t know but i obtain this error.

image
image1392Ă—181 18.1 KB

I have entered the credentials as you told me.
My server is an instance of akeneo in Aws

9

Can you past your workflow? And a screenshot of your workflow ?

10

@victormiranda your Akeneo is configured to use a self signed certificate so it can’t be trusted properly, You could look at using Lets Encrypt to create a cert for it or in your n8n project for hte HTTP Request enable the Ignore SSL Issues option.

11

Thanks @Christel_Doudet @Jon , its work!

12

Wonderful! Thanks, @Christel_Doudet and @Jon :sparkling_heart:

@victormiranda, can you please share the solution so that other members can easily find it? :slight_smile:

13

It was a problem with the akeneo certificate, adding the option Ignore SLL problems worked.