But when it runs it gives the error below on the App connect page.
I have tested it multiple times with different invoice numbers and the same error appears.
Have you tried this doing this manually with an actual in_XXXX number from stripe and using your SK_ key? If not, do so, and make sure you can successfully run and define the API schema.
If that works, it’s simply a case that 1 of your 2 parameters are wrong - inv_ or SK_
thanks for the reply. Yes I have tried manually entering the inv and the sk_ manually, the same error appears. Its really strange, because I run other stripe APIs without a problem (thanks to your previous help :). But its the send_invoice api that fails. It also fails if I use the built-in stripe wappler ‘send_invoice’ api. Same error.
It sounds to me like a wappler error - there is a lot of reference made to wappler lib etc.
@scalaris, I tested with insomnia and the API works fine using a test invoice. @George@Teodor , is this a #wappler-general:general-bugs?
I can’t get send_invoice to work with normal API server setup and also using the built in wappler send_invoice.
There error appears to be point to Wappler? But unsure.
Is there a way to force Wappler to recreate the dmxConnectLib?
PHP server model.
Yes I do I have Bearer along with the SK_value. My other APIs work and are a mix between the. Jolts in Wappler built in stripe API and normal API used to connect to Wappler.
After rebuilding the LIB, I still get the error. The query correctly outputs the invoice number, but fails not he API action.
The other APIs work.
Not sure what the issue is. Testing on Insomnia work find and updates Stripe correctly.
It’s a strange one. I use the latest wappler version with nodejs and if you want me to test it with your test keys and in_ number specifically, let me know. I don’t ever use that call in my code as stripe automatically sends invoices after transactions in live mode
it is a strange one. its not essential but desired. I am glad to know that stripe sends the invoice auto in live mode. The worst case they have a delay of 1 hour. But anyhow. I appreciate your help always @scalaris.
Hi @Patrick /@George , I noticed a recent auto update that was pushed a day or so ago for api.php? I updated it and it still causing the same error. However the api.zip you provided above works! So I am not sure if the wrong update was sent live? can you provide advise?
This is what comes up when I restarted wappler. Its asking to update api.php - is that because I manually replaced the file with the one Patrick provided?