| [reply] |
Or maybe even providing the code you've already written so someone has something to maybe actually look at and perhaps point out problem(s).
But it's probably that thing you did on line 134. It's ALWAYS line 134.
The cake is a lie.
The cake is a lie.
The cake is a lie.
| [reply] |
With most APIs, the most time will be spent on getting Authentication right, I've study more than a few Python clients so that is a good suggestion if that one works, just to see how they do the auth. You can link the Python code if your goal is to replicate the auth scheme. Better even, accurate developer docs :-) | [reply] |
I know I am late to the party, but I concur that dealing with authentication is 90% of the hurdle. I've had do all kinds of things like examine Python code before - not that it's easy to tease out. The general things you need tend to be the same like, MIME::Base64 and Digest::SHA, but the way they want you to combine strings (keys, usernames, password) and the headers they want you to provide are always a crap shoot.
I am not going to post the code because idk if it's correct and it seems wrong to do in the monastery, but chatgpt seems to be happy suggesting a Perl solution for this. If you make some progress and have questions, please report back.
update: this is awkward, I was gone so long I forgot I had replied to this and didn't even notice. hopefully the additional info is helpful | [reply] |