# Authenticate request with API key

**URL:** <https://integration.keap.com/t/authenticate-request-with-api-key/70321>\
**Category:** API Q&A\
**Tags:** oauth, api\
**Created:** [August 5, 2019, 9:34am UTC](https://integration.keap.com/t/authenticate-request-with-api-key/70321 "2019-08-05T09:34:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gabor\_Magyar](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/gabor_magyar/32/10648_2.png) [@Gabor\_Magyar](https://integration.keap.com/u/Gabor_Magyar)\
**Post date:** [August 5, 2019, 9:34am UTC](https://integration.keap.com/t/authenticate-request-with-api-key/70321/1 "2019-08-05T09:34:50Z")

</div>

Hey Guys!

I am working on an integration to use some of the API features in one of our application. The problem is that I cannot use the oAuth or the access\_token way to authenticate my requests so I would like to use the legacy XML-RPC API. The authentication is done but when I try to query to create a new contact with the official nodejs sdk ([GitHub - infusionsoft/infusionsoft-sdk-nodejs: A NodeJS SDK automatically generated from Infusionsoft API Swagger definitions.](https://github.com/infusionsoft/infusionsoft-sdk-nodejs)) I get these errors: `No method matching arguments: java.lang.String, java.lang.String, java.lang.Integer, java.lang.Integer, [Ljava.lang.Object;'`

What could be the problem? Is the legacy XML-RPC solution still works? Do we have any workarounds perhaps? Or can I use the new REST API with a single API key like in the legacy service?

Regards,  
Gábor