API DATA SOURCE and Curl Requests

[yarycling]

There are no transaction attempts in the dashboard. However, with the same config in the API schema, it works and I see the transaction in the dashboard.

[geoplugin]

@patrick - wappler uses stripe and so I’m guessing that wappler’s use of stripe implements wappler?
While while the wappler api might not handle such stripe requests out of the box, there must be a way? An encrypted key (to protect vars being passed to a server side script by anyone) is passed to a SSI script, which handles then the Stripe call via classic cURL means and gives the status in reply to wappler?

[George]

OK I see the problem you have.
You have to put the Stripe Authorization Bearer key within single quotes.

This is for all headers fields - if you don’t have dynamic values - always enclose them in single quotes.

So that should make it work

Also I wonder why you use API Form as Forms are using for submitting data to the API and you are just fetching data so in that case API Data Source will do better.

[Freddy_Blockchain]

wonderful! Was also wondering about that. I’ll try out some APIs with these bearer tokens! Thanx so much.

[George]

Well there you go:

API Connector components, how to use and connect REST/Curl API's

With the API Connector in Wappler, you have gained a lot of powers to directly connect to API’s and fetch data or call their actions. The API Connector is based on three components: API Data Source API Action API Form In this article you will learn when to use the different API components and how. API Data Source The API Data Source is the most simple component but powerful API component and gives you a way to fetch data from the API so you can use it on your page as dynamic data. A basic …

[yarycling]

Yes yes that’s it. I am getting something now. Thanks much

[Freddy_Blockchain]

I tried to connect to the API from Rossum.ai Invoice recognizionservice but not clear where to put autorization in wappler but get 404… via CURL , python no problem…

[s.alpaslan]

Name : authorization
Value : ‘secret key’

[Freddy_Blockchain]

tried it. still 405 method now allowed… confused now with api server side, client side and or api form/api action… I guess I need to use API Action and maybe thats why I get that 405

[patrick]

Header Name: Authorization
Header Value: secret_key poqMqDC...

I removed the first image of your post since it showed the whole secret key.