I did see another post about this and would like to state that this API IS an https and it is a rest API. Currently I have all my data set up in a JSON template column:
Now I have no experience with reqbin but I went there, copy pasted exactly what is in my template JSON column into the content there. Added in the singluar header(content-type) and copy pasted the exact endpoint in my API⌠and it worked perfectly:
I doubt this relates to CORS, but other than that I donât know why it wouldnât work, providing you have the correct setup and the response time of 1133 ms in the last screenshot.
Have you tried configuring that as an action opposed to a column?
Tried it, still didnât. So I tried their schema, which is literally just a GET API call with one header. No body. Just an endpoint, via GET method, content-type:application/json. Once again, complete time-out. If I add it as a button action(watched Robert and Darren Humphries videos on that and it works the same as the column so I know thats correct too) the button just goes light for 30 seconds then dark again and nothing happened, i.e timed out. And once again if I literally just copy my endpoint into reqbin.com, and add that singluar headerâŚ
35501 are the last numbers after the : in that endpoint, not sure on the relevance but yes an answer would be appreciated. If Glide does enforce port 443, is that something the API could change on their end(to your knowledge I understand some differ). Basically will it still be possible to form a connection if this is the issue.
Yes, anything that comes after the colon and the first forward slash is the port number.
443 is the default port for HTTPS, but itâs not uncommon for custom port numbers to be used.
I donât know if Glide force 443 or not, that was just speculation. But it would explain the timeout.
If that is the case, then youâd either need to ask the provider if they can provide an endpoint that listens on 433, or hope that Glide might add support for custom ports.
Anyway, all speculation. Best to wait for a definitive answer.
Okay thanks, while I wait for a response can I ask: to your knowledge if Glide does enforce a 443(speculation) and the API keeps their custom port number is there any other way to connect if Glide doesnât allow for custom ports(speculation)? So if the API wonât change and neither will Glide, would there be another way?
