Wrong api_key or signature with DATES

15 views
Skip to first unread message

Juan Carrey

unread,
May 28, 2011, 6:24:55 AM5/28/11
to producteev-api-discuss

Hi,

I'm new on this group, I'm testing this API, and I get always a "403
Forbidden" (in json format) and a "Wrong api_key or signature" in XML
format, whenever I add a Date param.

If I try to encode all parameters for signature, I get a 403 Forbidden
on the User Logging requests, (I encode the email), so it doesn't
work !
If I try to not encoding any parameter I still getting a 403
Forbidden....

But, surprisely, if I encode the Dates and JUST the dates, everything
works perfect !

Please, be more consistent.

Thank you !

Thomas Bonnin

unread,
May 31, 2011, 9:57:00 AM5/31/11
to Juan Carrey, producteev-api-discuss
Hi,
Can you give me examples of refused requests so we can look into it.

Thomas Bonnin

Juan Carrey

unread,
May 31, 2011, 1:02:34 PM5/31/11
to producteev-api-discuss
Any request with a date, which contains " .... +200", so, if I encode
all parameters of all requests, whenever i try to use the login
request, i get a 403 because of the Api validation failed when the "@"
of login username, is encoded to %XX . It works perfect if I don't
encode at all any parameters.

But, when i try to invoke a GET with any date parameter ("Sun,
******** +200" ) , if i do not encode this parameter i get the 403,
but if I encode this, and ONLY this parameter, it works OK.

I'll put more details when I arrive to my home, i don't have details
here.

Thanks for your time

Juan

On 31 mayo, 15:57, Thomas Bonnin <thomas.bon...@gmail.com> wrote:
> Hi,
> Can you give me examples of refused requests so we can look into it.
>
> Thomas Bonninwww.producteev.com
>

Thomas Bonnin

unread,
Jun 8, 2011, 10:09:54 AM6/8/11
to Juan Carrey, producteev-api-discuss
Sorry for the late reply.
All parameters should be url encoded. However it mights works if you request doesn't contains any unsafe ASCII characters. 
Encoded "@" character (%40) is probably not the source of your problem. Multiple api calls are made every day with it and it works fine.
Can you send us a specific example of request that get a 403 error?
Thank you

Thomas Bonnin

Juan Carrey

unread,
Jul 8, 2011, 2:11:03 PM7/8/11
to producteev-api-discuss
Its solved.

URLEncoder of Java doesn't encode "+" simbol, and as parameter it was
resolved as white space.
Reply all
Reply to author
Forward
0 new messages