How to Connect to a API with dynamic

dataservices job design
1

Hi,

I have a requirement to connect to a API that uses the below method - is this possible using Data services and if so how is it done ??

Endpoint er https://yyyyyyy.xxxxx.com/api/v2

Function
https://yyyyyyy.xxxxx.com/api/v2/users

API key:
zaQs8dmdydlJ3Ygohghm4UPJM7vCZJGWcWDSf1N6gan3WZ4ltUPHnfglLniCEPxx5pP

The API key should be used in the header in your request:
x<generated<at:YYYYMMDDHHMMSS
x<hash: <base64(hash(time, api key)>

"x<generated<at” the header must be in UTC time.

"x<hash” will be verificed based on the following PHP code:
base64_encode(hash_hmac('sha512’, ‘’, ‘’));

ekaj (BOB member since 2017-01-31)

2

Is this example something similar to what you want?

https://blogs.sap.com/2016/06/07/consuming-rest-web-service-in-sap-data-services-using-web-service-rest-datastore/

If it is, then you could do it, you would just need to translate the PHP functions (base64_encode and hash_hmac) over into DS if they do not exist already.

  • E

eepjr24 :us: (BOB member since 2005-09-16)

3

Hi,

The issue is to get access to the API (login) - even if I create the .WADL file and import it I am still missing the possibility to enter the dynamic API key hashed and encoded in the call to the API.

The login looks like header auth. to me but I am not sure it is possible to do the encoding and the concatenation of the API key and the timestamp as I described above.

ekaj (BOB member since 2017-01-31)

4

Not sure what you mean here? If you can get the WADL, it will tell you the parameters it takes as input (including login information if applicable) and then you just build the message as in Step 3 of the above link. It does not have to be a flat file input, you can has as much or as little processing to create name value pairs for consumption by the API as you desire.

  • E

eepjr24 :us: (BOB member since 2005-09-16)

5

SAP Data Services supports various authentication schemes, including oAuth 1.0 and 2.0.

However:

I suspect that this may be part of your problem? You may want to check the Data Services Integrator Guide, in section 8.2.1.2.1 “Authorization schemas for REST”. I only have the Integrator Guide for DS 4.2 SP07 here, you may also want to check the SP08 version to see if this support was added in the latest service pack release.

If you can’t get it to work directly or natively, you can also consider using Python by using an User Defined Transformation - this will require the full SAP Data Services license, it’s not accessible under the SAP Data Integrator License.

If that fails you can always revert to using a script language of your choice and incorporate that into your ETL jobs. I’ve used both external Python and R scripts for a number of tasks (mostly in the area of predictive analysis and text scraping) and incorporated those seamlessly into my ETL jobs.

ErikR :new_zealand: (BOB member since 2007-01-10)