"Enrich Data by Webservice with HTTP Header"

NamSorNamSor Member Posts: 6 Contributor II
edited June 2019 in Help
In the tutorial 'RapidMiner to enrich Gender data', the API does not require authentication:
http://namesorts.com/2014/04/23/rapidminer-to-enrich-gender-data/

But (say you would like to use Mashape or some other auth method) how do you specify an API Key HTTP Header in the RapidMiner Webservice operator?

Thanks!
Elian

Answers

  • JEdwardJEdward RapidMiner Certified Analyst, RapidMiner Certified Expert, Member Posts: 578 Unicorn
    If you put the header information in the Request Properties area, that should do the trick. 
  • ighybooighyboo Member Posts: 26 Contributor II
    Has anyone managed to solve this issue?

    I found the same/similar question on StackExchange and I wrote a question (specific to mashape) on this forum but no answer yet..
    I'm now trying to pass OAuth parameters to the Twitter API but had no luck in passing the right header format despite various different attempts




  • ighybooighyboo Member Posts: 26 Contributor II
    Anyone who can help with this? It's driving me crazy!  >:(

    HaHaHaHa
  • NamSorNamSor Member Posts: 6 Contributor II
    Hi,

    You no longer need to worry about HTTP headers, as you can now use NamSor Onomastics Extension (from RapidMiner MarketPlace). Tutorial here
    http://blog.namsor.com/2014/09/10/video-tutorial-how-to-extract-the-gender-of-personal-names-using-rapidminer/

    There are currently two operators,
    Gender : to infer the likely gender of a personal name;
    Origin : to infer the likely origin of a personal name.

    Best,
    Elian
  • JEdwardJEdward RapidMiner Certified Analyst, RapidMiner Certified Expert, Member Posts: 578 Unicorn
    Looking forward to your talk at RapidMiner world.
Sign In or Register to comment.