Error 400004: Invalid KC-API-PASSPHRASE

[wilsonsuryajaya]

Hi there. First of all, thanks for the wonderful library.

I encountered the following issue: "400004: Invalid KC-API-PASSPHRASE" when testing the REST-API on the sandbox environment, while the Socket Client that uses the same credential doesn't. This is the testing code

static async Task Main( string[] args )
{
    // --- The REST API fails with 400004: Invalid KC-API-PASSPHRASE ---
    var kucoinClient = new KucoinClient( new KucoinClientOptions()
    {
        ApiCredentials = new KucoinApiCredentials( Properties.Resources.API_KEY, Properties.Resources.API_SECRET, Properties.Resources.API_PASSPHRASE ),
        LogLevel = LogLevel.Trace,
        RequestTimeout = TimeSpan.FromSeconds( 60 ),
        FuturesApiOptions = new KucoinRestApiClientOptions
        {
            ApiCredentials = new KucoinApiCredentials( Properties.Resources.FUTURE_API_KEY, Properties.Resources.FUTURE_API_SECRET, Properties.Resources.FUTURE_API_PASSPHRASE ),
            AutoTimestamp = false,
            BaseAddress = KucoinApiAddresses.TestNet.FuturesAddress
        }
    } );

    var accounts = await kucoinClient.FuturesApi.Account.GetAccountOverviewAsync();
    if ( !accounts.Success )
        Console.WriteLine( "Request failed: " + accounts.Error );
    else
        Console.WriteLine( "Result: " + accounts.Data );
    // --- End of REST API test ---

    // --- The SocketClient however is able to subscribe and get the market data ---
    var kucoinSocketClient = new KucoinSocketClient( new KucoinSocketClientOptions()
    {
        ApiCredentials = new KucoinApiCredentials( Properties.Resources.API_KEY, Properties.Resources.API_SECRET, Properties.Resources.API_PASSPHRASE ),
        LogLevel = LogLevel.None,
        FuturesStreamsOptions = new KucoinSocketApiClientOptions
        {
            ApiCredentials = new KucoinApiCredentials( Properties.Resources.FUTURE_API_KEY, Properties.Resources.FUTURE_API_SECRET, Properties.Resources.FUTURE_API_PASSPHRASE ),
            BaseAddress = KucoinApiAddresses.TestNet.FuturesAddress
        }
    } );

    var cts = new CancellationTokenSource();
    var subscriptionResult = await kucoinSocketClient.SpotStreams.SubscribeToTickerUpdatesAsync( "BTC-USDT", DataHandler, cts.Token );

    if ( !subscriptionResult.Success )
    {
        Console.WriteLine( "Failed to connect: " + subscriptionResult.Error );
        return;
    }

    Console.ReadLine();
    cts.Cancel();
}

private static void DataHandler( DataEvent<KucoinStreamTick> updateData )
{
    Console.WriteLine( $"{updateData.Data.Sequence},{updateData.Timestamp.ToString( "dd/MM/yyyy HH:mm:ss.fff" )},{updateData.Data.Symbol},{updateData.Data.LastPrice},{updateData.Data.LastQuantity}" );
}

Below output shows that the REST API fails to get the account overview, but the Socket Client is able to subscribe and receive real-time market data using the same credentials.

Would you have any clue what might be the cause of this issue?

Thank you

[JKorf]

Hi, the websocket for market data doesn't require any credentials, so it makes sense that it can connect without issue.

I assume you double checked the credentials? The error message indicates an issue with those. Also, you might need seperate credentials for the futures API (can't remember from the top of my head if this is the case for Kucoin), so it might be that you're trying to use your real credentials for the sandbox environment.

[wilsonsuryajaya]

Thanks for the prompt answer.

I created an API key and another separate Future API key for the sandbox environment as shown below (I have just started so I haven't generated any keys for live yet).

I tried to search around for people reporting the same issues and tick the following boxes:

• Double-checked the API key and Secret key
• Make sure to use passphrase and not the trading pin (although I tried both)
• Tried using the wrong key or passphrase which give different error "400003: KC-API-KEY not exists"
• Tried deleting and recreating the API and Future API keys a few times (copy paste everything)
• I also read someone tried using plain passphrase text for v1, but for v2 we need to use SignHMACSHA256 and 64 base

but still getting the same issues.

[wilsonsuryajaya]

Hi I don't know what I did wrong previously but today I tried creating new APIs with simple passphrase and it is working now. Thanks for the help anyway.