Quick Poll: What’s the #1 Thing That Trips You Up in the Investec API?

[programmable-banking-community]

Hey team 👋

We always want to kill the biggest pain-points for peeps, and the fastest way to find them is to ask you straight up.

What trips you up most often when working with the Investec API?

Important

Even if your main pain-point isn’t on the list, pick the closest option and drop the details in a comment. The stories behind the vote are pure gold.

What happens next?

• We’ll publish the results and the actions we’re taking.
• Expect follow-ups in docs, examples, and maybe even a new SDK if that’s what the data screams for.

Thanks for keeping us honest. Let the voting - and the venting - begin! 🚀

[petersmythe]

As mentioned to Nick: x-api-key needs to be in the OAuth2 request header, otherwise a perfectly looking access_token is returned, but it does not work.

[schoemanpj]

A couple of years ago when API's started for us there was only one credential set for an individual only requiring a Client Id and Secret. The x-api-key was added to define the consent model the token has access to and allow one to create multiple keys on a credential set. Allowing for backwards compatibility the Client Id and Secret still authenticates you where the key defines the authorisation the key will give you.

[petersmythe]

PS, I love that you are so responsive to feedback - it is much appreciated!

[cyrus-za]

Definitely authentication. It took me a while to realize that it works this way. It is completely different from any other api I've ever used. It's mixing api key authentication with oauth. It should be one or the other. Not a mix of both