GoCardless API: Can't send secret_key & secret_id

toby2 · 2024-10-21T12:16:40.473Z

Been trying to connect GoCardess’s bank accounts but cannot get it to work despite the postman working and API call working itself.

Postman

The issue is specifically calling this:

curl -X POST "https://bankaccountdata.gocardless.com/api/v2/token/new/" \
  -H "accept: application/json" \
  -H  "Content-Type: application/json" \
  -d "{\"secret_id\":\"88674960-6cf0b59a84\", \"secret_key\":\"c06dc9be3bbd5b920593d366f728ab61716026e3815cdba69bcaf485d57de0f8bbd166fef235910ff02c411c430287f6e555537b8\"}"

and the error ends up being:
* Raw response for the API Status code 400 {"secret_id":["This field is required."],"secret_key":["This field is required."],"status_code":400}

So it looks like the secret_id and secret_key are not getting passed.

This is configured as a JSON body type.

If you try and just have the same JSON and use this link: https://bankaccountdata.gocardless.com/api/v2/token/new it will work (well it won’t because the key’s content is edited, but the keys are sent through)

The docs are the following: Bank Account Data - Quickstart Guide

bubble is just not sending through the keys… any ideas?

Toby

Jici · 2024-10-21T13:00:48.358Z

Can sou share api connector settings? Did you add content type header?

toby2 · 2024-10-23T16:12:29.891Z

yup all that is setup.

Content-Type: application/json

Checked for spelling, etc.

It triggers, just the JSON doens’t get sent.

T.

Jici · 2024-10-23T16:40:33.231Z

But how did you set the json? Please share a screenshot.

Jici · 2024-10-23T17:06:42.978Z

If you copied and paste the escaped JSON… this is why it’s not working probably

{
  "secret_id": "yoursecretid",
  "secret_key": "yoursecretkey"
}

By the way, this kind of auth can be used in custom oauth2 token.

toby2 · 2024-10-23T17:21:39.082Z

This is the setup:

image1718×1112 93.7 KB

Jici · 2024-10-23T17:33:24.403Z

Working for me:

screenshot-bubble_io-2024_10_23-13_23_54901×648 33.9 KB

Any shared header that could create issue?

toby2 · 2024-10-23T17:42:16.934Z

What did you use for the header? This is super weird…

I tried with this:

image1820×1308 179 KB

With the JSON being the same as you…

T

Jici · 2024-10-23T17:48:11.919Z

I didn’t add any because bubble by default add one. And for Accept, doesn’T seem to be really mandatory.

toby2 · 2024-10-23T18:08:23.194Z

Well whatever you did is magic… cause I can’t see how it works…

Jici · 2024-10-23T18:25:19.307Z

Start from scratch with a new API and call. In some rare case, Call get corrupted by attempt you did.

toby2 · 2024-10-23T18:56:18.505Z

yup did that - one a new project + even a new plugin…

Jici · 2024-10-23T18:57:59.241Z

Always the same error?

That sound very strange…

toby2 · 2024-10-23T19:20:06.000Z

Yup same thing. Just a 400 the Jain isn’t being seen.

If I use oauth2 custom token I get that the secret_key is wrong… but it’s correct… soo that doesn’t help.

T

Jici · 2024-10-23T20:42:04.745Z

I’ve checked and finally doesn’t think it will work for custom token because this is not returning the token_type parameter and doesn’t response with access_token but just “access” instead. Sorry.

Next step to debug this is to create a requestbin.com (or other similar tool) and send the request there and inspect

toby2 · 2024-10-24T15:07:33.304Z

Found it:
Importing the cURL will trim the trailing /

This means that the call wasn’t working correctly, and pointing to the wrong API. Needed /new/ instead of /new

Thanks bubble! grrr