search

banboo-data / RCriteo

Loading Criteo Campaign Data into R
http://jburkhardt.github.io/RCriteo/
Other
6 stars 3 forks source link

Criteo REST API #10

Open aleDsz opened 5 years ago

aleDsz commented 5 years ago

The actual SOAP API is going to be deprecated, do you have plans to update the package to support the new REST API?

If not, may I can contribute for this.

Article: https://support.criteo.com/hc/en-us/articles/360001226125-Testing-Criteo-Marketing-API

jburkhardt commented 5 years ago

@aleDsz Thank you for the notice! Yes, you are welcome to contribute. Just fork the repository and develope on a new branch.

jburkhardt commented 5 years ago

@aleDsz Could you provide more information about a deprecation schedule and is there a migration guide?

Amatcov commented 5 years ago

Hi folks! Please help on authentication issue:

That's the piece of authentication code I am using:

Where 'user' is - Criteo REST API user, same for the password

authToken <- doCriteoAuth(user = "xxxxi-xxx-xxx-xxx-xxx-xxxxxxxx", password = "xxx:xxxxxxxx", company = "Walrus", app = 'Walrus', version = "3.6")

Here's the error:

Error in function (type, msg, asError = TRUE) : error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

Could you advise if we need to use API user's credentials to access Criteo REST API?

Should we use any OTHER application name? - as the app. argument is compulsory for the function

jburkhardt commented 5 years ago

The package is functioning and in productive usage! I think Criteo has to create an API access for you. If you have this already, you will find the appName in the criteo accout settings. doCriteoAuth returns an authToken. Furthermore, you will need an appToken which you can get from your Criteo Account Manager. Read more here https://github.com/jburkhardt/RCriteo/issues/2 Hope this helps!