SDK createTransferMethod Json-Cache-Token sending as param

[raffibag]

Hi there. I'm working on a project that's using the embedded widget to allow users to set up a transfer method. When using the SDK to make the createTransferMethod call, the Json-Cache-Token appears to be delivered as a param; and not in the Headers, as specified by your API documentation. When I made the same call using fetch/Axios, it worked fine and returned the expected 201 response.

For reference, here is the api call as I had it configured (note:

client.createTransferMethod(userToken, jsonCacheToken, data, callback => {
    // response handling
})

And this is the how the call was posted (tokens intentionally obfuscated/shortened):

https://api.sandbox.hyperwallet.com/rest/v3/users/usr-55555/transfer-methods?Json-Cache-Token=95e73149-55555

The result of the issue was that, as expected, the API call to HW returned an error (as it was unable to parse the data contained in the cache token).

Not sure if this can be replicated - or if I'm missing something, but all other SDK calls seem to be working fine. For the time being, I'll keep the fetch option in place. Thanks much.