"Enrich Data by Webservice with HTTP Header"

User: "NamSor"
New Altair Community Member
Updated by Jocelyn
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

Find more posts tagged with

Sort by:
1 - 5 of 51
    User: "JEdward"
    New Altair Community Member
    If you put the header information in the Request Properties area, that should do the trick. 
    User: "ighyboo"
    New Altair Community Member
    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




    User: "ighyboo"
    New Altair Community Member
    Anyone who can help with this? It's driving me crazy!  >:(

    HaHaHaHa
    User: "NamSor"
    New Altair Community Member
    OP
    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
    User: "JEdward"
    New Altair Community Member
    Looking forward to your talk at RapidMiner world.